-
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 ] |
There is already a separate bug report that pipeline polling does not ignore commits from specific users.
Can you provide a job definition which shows the problem you're describing? I spent last weekend investigating with a freestyle job and a multi-branch pipeline job and was unable to duplicate the type of problem you describe with those jobs. Refer to JENKINS-41906 (and my jenkins-bugs repo) for my notes on my attempt to duplicate the problem.
I doubt this is due to a recent change in the plugin, since there have been no changes in the polling area. However, the pipeline support (with the exclusions) was only added in the last 12 months, so it may never have been working the way you expect in pipeline.