aajimal
commented
3 years ago We are experience this issue as well:
- Bitbucket v7.8.1
- Bitbucket Branch Source v2.9.9
Closed wickkidd closed 1 year ago
aajimal
commented
3 years ago We are experience this issue as well:
KalleOlaviNiemitalo
commented
3 years ago The "Did not schedule build for branch:" message seems to come from MultiBranchProject.scheduleBuild. So ParameterizedJobMixin.scheduleBuild2 presumably returned null.
If you click "Build Now" on the pull request, does it build then?
ParameterizedJobMixIn.ParameterizedJob.isBuildable checks ((Job) this).isHoldOffBuildUntilSave(), which might somehow have been left in the wrong state. Can you check that via the Script Console?
Thilaknath
commented
3 years ago @KalleOlaviNiemitalo I am facing the same issue. When I click Build now, The project builds.
Even though I have set the Automatic trigger to discover PR-.* and develop branch. Whenever I create a new PR the job doesn't trigger, It also doesn't trigger when there are push events to the develop branch, Not sure how to go about it ?
@bitwiseman Can you share your thoughts on this issue.
Thilaknath
commented
3 years ago @wickkidd Do you have a solution for this ?
aajimal
commented
2 years ago Manually triggering the build has helped but it is obviously not scalable. We have also found that deleting the PR and re-creating it has helped.
So it does seem that maybe there is something amiss in the PR updated hook when fired (i.e. when a PR is opened and commits are added over time). However, this does not seem to happen in every case of updated PRs.
wickkidd
commented
2 years ago @wickkidd Do you have a solution for this ?
Yes. We're moving to github workflows/actions https://docs.github.com/en/actions/learn-github-actions 💪
As others have suggested, manual builds work as do builds triggered via push through the webhook (which is what we're currently using). The problem with using push is that there are many times when a dev simply wants to save their work by pushing up a branch they don't intend to have built and perhaps never even merged, yet it will be built anyway. This causes undesired resource usage which limits how many resources are available for builds we do want and it costs money as well.
Despite moving on from jenkins for our use case, I'm still interested in seeing PR triggers work in jenkins as I'm sure it and I will cross paths again sooner than I'd think. FWIW, most of the issues I've ever had with jenkins aren't actually with the core software, but rather with the plugins. Not knocking the generous plugin authors. Just noting where the issues tend to be found.
lifeofguenter
commented
2 years ago Is this still an issue with the current release? (context: https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/527#issuecomment-986227458)
rkivisto
commented
1 year ago If someone is encountering this issue, when you see:
Did not schedule build for branch: PR-...One important item to check is at the organization folder level: the configuration entry Automatic branch project triggering -> Branch names to build automatically. Make sure this regex is either .* or has PR-\d+ inside of the regex.
Version report
Bitbucket Server: v7.5.1
Jenkins and plugins versions report:
Reproduction steps
Steps
1: Configured jenkins with a Team/Project using defaults 2: Filtered the Team/Project down to a single repo
testapp(until I get builds working properly from webhooks) 2: Filtered out building based on branch indexing with the exception of 3 named, long running/main branches (which do build correctly from indexing)Additional (relevant) Jenkins configuration:
Results
Expected result:
For the job to build as a result of the webhook firing (branch
PR-14based on the associated PR in this particular case)Actual result:
The webhook fires successfully (http 200 in bitbucket > webhook details > Pull request opened > last success link).
For a new PR (
pr:opened):For an updated PR (
pr:from_ref_updated):Notes:
While "Met criteria" was stated for branch
PR-14for both events, according tojobs/Brian\'s\ Test\ Team\ Project/jobs/testapp/indexing/events.logit still read "Did not schedule build for branch: PR-14."This seems nearly identical to the issue @rnkhouse had here https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/315#issuecomment-638293537 with the main differences (afaik) being that the branch in question for my issue is based on a PR and the versions of things are a bit newer.
I did my best to compile the relevant information based on other issues here, stack, the interwebs at large, etc... If I missed anything, please let me know. My initial thought is that there might be a setting somewhere that I've made incorrectly since it claims "Met criteria" and "Changes detected" (with the actual sha of the change in the case of an update), but then states that it did not schedule a build. Any direction would be greatly appreciated. Thanks.