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
What Operating System are you using (both controller, and any agents involved in the problem)?
RHEL / CentOS, Linux EL7
Reproduction steps
Let's define a GitHub PR status as (ContextName, Result).
Setup a Jenkins pipeline with GitHub Pull Request Builder enabled
Create a PR in the GitHub repo to trigger a Jenkins job (this would trigger a job that exposes in the GitHub page a "pending" state for the status with the initial name, let's say "default") -> GitHub PR Status is then (default, Pending)
Update the Jenkins pipeline to change the status context of the ghprb integration (say from "default" -> "Jenkins Build")
The Jenkins job started by step 2 finishes now (after step 3).
Expected Results
I would expect to have only one status on the build, either one of the two cases for the check after finishing the Jenkins job:
The Jenkins config did not propagate to the job that was in progress, and the job gets to see the status (Default, Passed) in GitHub; the Jenkins config update will then only affect future jobs
The Jenkins config propagated to the job that was in progress, and the job gets to see only the updated context name at the end of the job (Jenkins Build, Passed)
Actual Results
The Job ends up generating 2 statuses that persist after the job is done for the GitHub PR: (Default, Pending) and (Jenkins Build, Passed).
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
RHEL / CentOS, Linux EL7
Reproduction steps
Let's define a GitHub PR status as (ContextName, Result).
Expected Results
I would expect to have only one status on the build, either one of the two cases for the check after finishing the Jenkins job:
Actual Results
The Job ends up generating 2 statuses that persist after the job is done for the GitHub PR: (Default, Pending) and (Jenkins Build, Passed).
Anything else?
No response
The text was updated successfully, but these errors were encountered: