-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Jenkins 2.315, Bitbucket Plugin 223.vd12f2bca5430
I think this bug was caused by the change in https://issues.jenkins.io/browse/JENKINS-49414 .
Preconditions:
1. Using Bitbucket plugin with setting "Build when a change is pushed to BitBucket"
2. "Build on branch created" false (default)
Problem / steps to reproduce:
- Create new branch locally
- Create commit to new branch
- Push new branch to origin
with Bitbucket Plugin 223.vd12f2bca5430 -> Job is not triggered. Should be, because there's also new commit.
with Bitbucket Plugin 1.1.29 -> Job is triggered
[JENKINS-69670] JENKINS-49414 regression - build is not triggered when new branch is pushed with new commit(s)
Description |
Original:
I think this bug was caused by the change in https://issues.jenkins.io/browse/JENKINS-49414 .
Problem: If you push new branch with new commits, build is not triggered. If you push new branch first before adding any new commits, and then push your commits afterwards, build is triggered normally. This never happened with older version of the plugin which didn't have this new boolean "Build on branch created". |
New:
I think this bug was caused by the change in https://issues.jenkins.io/browse/JENKINS-49414 .
Preconditions: 1. Using Bitbucket plugin with setting "Build when a change is pushed to BitBucket" 2. "Build on branch created" false (default) Problem / steps to reproduce: # Create new branch locally # Create commit to new branch # Push new branch to origin -> build is not triggered. Should be, because there's *also* new commit. and, if done like this: # Create new branch locally # push to origin # --> No build triggered (which is correct) # create commit # push to origin # --> Build triggered |
Description |
Original:
I think this bug was caused by the change in https://issues.jenkins.io/browse/JENKINS-49414 .
Preconditions: 1. Using Bitbucket plugin with setting "Build when a change is pushed to BitBucket" 2. "Build on branch created" false (default) Problem / steps to reproduce: # Create new branch locally # Create commit to new branch # Push new branch to origin -> build is not triggered. Should be, because there's *also* new commit. and, if done like this: # Create new branch locally # push to origin # --> No build triggered (which is correct) # create commit # push to origin # --> Build triggered |
New:
I think this bug was caused by the change in https://issues.jenkins.io/browse/JENKINS-49414 .
Preconditions: 1. Using Bitbucket plugin with setting "Build when a change is pushed to BitBucket" 2. "Build on branch created" false (default) Problem / steps to reproduce: # Create new branch locally # Create commit to new branch # Push new branch to origin with Bitbucket Plugin 223.vd12f2bca5430 -> Job is not triggered. Should be, because there's *also* new commit. with Bitbucket Plugin 1.1.29 -> Job is triggered |
Assignee | New: Tzach Solomon [ tzach_solomon ] |
And because this new setting "Build on branch created" is still not available via jenkins DSL this is problematic and we need to still keep Bitbucket Plugin 1.1.29.