- 
    
Improvement
 - 
    Resolution: Fixed
 - 
    
Critical
 - 
    None
 
Commit https://github.com/jenkinsci/github-branch-source-plugin/commit/5a98d2a885aa951087ba329acdc560bc1e6b7062 just broke the workflow for us.
We have our protected branches set up to check for context "Jenkins", so a successful build (from our organisation/multibranch projects) is enforced before merging. Through the mentioned commit, we now get "Jenkins job <whatever>" as notification context, on which we cannot protect anymore.
Please add an option to choose if the default context should contain the job name or not.
I am aware that you can set a custom context through the GitHubCommitStatusSetter step, but its not a viable and clean solution for us, as we would have to change hundreds of Jenkinsfiles.
- blocks
 - 
                    
JENKINS-33161 Allow merge commits to be built from origin PRs
-         
 - Resolved
 
 -         
 
- duplicates
 - 
                    
JENKINS-37100 GitHub status check "context" should be constant
-         
 - Closed
 
 -         
 
- is duplicated by
 - 
                    
JENKINS-36848 Unable to pass Jenkins status check if GitHub has protected branches
-         
 - Resolved
 
 -         
 - 
                    
JENKINS-36602 Github Status in a organization project should be the same
-         
 - Resolved
 
 -         
 
- is related to
 - 
                    
JENKINS-35453 Allow disabling the default commit status notifier
-         
 - Resolved
 
 -         
 
- relates to
 - 
                    
JENKINS-65822 Support multiple github checks against the same PR
-         
 - Open
 
 -         
 - 
                    
JENKINS-46119 Use the job name in context string
-         
 - Resolved
 
 -         
 
- links to
 
- mentioned in
 - 
                    
Page Loading...