-
Bug
-
Resolution: Not A Defect
-
Blocker
-
Jenkins 2.32.2
Git plugin 3.0.5
Attached are images of the configuration that I have set up for the pipeline.
In 'branches to build' I indicated the dev branch for my pipeline which should be triggered by a push to my repo in Github. However, whenever a new commit is pushed to the repo, the webhook triggers both my dev branch pipeline and the master branch pipeline as can be seen here
This problem is compounded by my Jenkinsfile that does a new commit to the branch after a successful build, hence, I have a build that will run indefinitely.
The problem with 'polling ignores commits..', I believe, may be related to this issue.
[JENKINS-42020] branches to build specifier broken
Ralph A
created issue -
Ralph A
made changes -
| Attachment | New: Screenshot from 2017-02-14 13-56-31.png [ 35949 ] |
Ralph A
made changes -
| Attachment | Original: Screenshot from 2017-02-14 13-56-31.png [ 35949 ] |
Ralph A
made changes -
| Attachment | New: Single git push triggers all projects watching the repo.png [ 35950 ] |
| Assignee | Original: Mark Waite [ markewaite ] |
Ralph A
made changes -
| Assignee | New: Mark Waite [ markewaite ] |
Ralph A
made changes -
| Assignee | Original: Mark Waite [ markewaite ] |
Ralph A
made changes -
| Attachment | New: pipeline-issue-01.png [ 35960 ] |
Ralph A
made changes -
| Attachment | New: pipeline-issue-02.png [ 35961 ] |
Ralph A
made changes -
| Description |
Original:
I have 2 projects set up on standalone pipelines watching the same repo, one for a dev branch and one for master. Previously, when I push to my dev branch it triggers the dev pipeline and when a branch is pushed/merged to master, it triggers the master pipeline. Now, this is no longer the case. It seems like the 'branches to build' functionality is no longer respected and whenever a branch is pushed to the repo, it triggers both pipeline projects. In addition, 'polling ignores commits..' seem to be broken as well. After Jenkins is finished running the build for the pipeline, it pushes some changes to the repo and since 'polling ignores commits..' no longer function, it causes a never ending cycle of builds. If this is unrelated to the issue, I'll open a separate ticket |
New:
I have 2 projects set up on standalone pipelines watching the same repo, one for a dev branch and one for master. Previously, when I push to my dev branch it triggers the dev pipeline and when a branch is pushed/merged to master, it triggers the master pipeline. Now, this is no longer the case. It seems like the 'branches to build' functionality is no longer respected and whenever a branch is pushed to the repo, it triggers both pipeline projects. In addition, 'polling ignores commits..' seem to be broken as well. After Jenkins is finished running the build for the pipeline, it pushes some changes to the repo and since 'polling ignores commits..' no longer function, it causes a never ending cycle of builds. If this is unrelated to the issue, I'll open a separate ticket |
Ralph A
made changes -
| Attachment | New: pipeline-issue-01.png [ 35962 ] | |
| Attachment | New: pipeline-issue-02.png [ 35963 ] |