The issue you’re running into is that Jenkins is reporting the branch build as successful right away, so GitHub (or your SCM) thinks the required check has already passed, even though the actual PR build hasn’t finished. The way around this is to separate the two builds so that only the PR build posts the status that’s marked as required for merging. In Jenkins, you can configure the job or pipeline that runs on pull requests to post its own distinct status, something like “Jenkins PR Build,” instead of reusing the branch build status. Then in your repository settings, you set that PR-specific status as the required check before merging. That way, the merge button won’t unlock until the PR build is done, and the quick branch build won’t cause false positives. If you’re using the GitHub plugin or multibranch pipelines, make sure the PR event triggers and reports correctly so Jenkins is always validating the merge commit, not just the branch head. https://dhcmenu.com/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.