You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently , there is no difference for "Status checks name". The default "Jenkins" name is used for both push and pull. But in our case the stage that are run for push and pull are different. it will be great if the status name is appended with _push or _pull based on event.
What Operating System are you using (both controller, and any agents involved in the problem)?
jenkins server is a docker container with pipeline running on different nodes
Reproduction steps
run both branch job and pull request job. Result of the checks api will overlap
Expected Results
Both branch and pull request has different entry
Actual Results
both results overlap. sometimes only branch result is published as in progress even after completion
Anything else?
No response
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered:
I was talking about GitHub commit(push) and changes in a pull request. When the branch has pull request, the name should be Jenkins_pull and for commit or push it should be Jenkins_push
Jenkins and plugins versions report
currently , there is no difference for "Status checks name". The default "Jenkins" name is used for both push and pull. But in our case the stage that are run for push and pull are different. it will be great if the status name is appended with _push or _pull based on event.
What Operating System are you using (both controller, and any agents involved in the problem)?
jenkins server is a docker container with pipeline running on different nodes
Reproduction steps
run both branch job and pull request job. Result of the checks api will overlap
Expected Results
Both branch and pull request has different entry
Actual Results
both results overlap. sometimes only branch result is published as in progress even after completion
Anything else?
No response
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: