Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Blocker
-
Resolution: Not A Defect
-
Component/s: github-plugin
-
Environment:Jenkins 2.32.2
Git plugin 3.0.5
-
Similar Issues:
Description
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.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Attachment | Screenshot from 2017-02-14 13-56-31.png [ 35949 ] |
Attachment | Screenshot from 2017-02-14 13-56-31.png [ 35949 ] |
Attachment | Single git push triggers all projects watching the repo.png [ 35950 ] |
Assignee | Mark Waite [ markewaite ] |
Assignee | Mark Waite [ markewaite ] |
Assignee | Mark Waite [ markewaite ] |
Attachment | pipeline-issue-01.png [ 35960 ] |
Attachment | pipeline-issue-02.png [ 35961 ] |
Description |
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 |
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 |
Attachment | pipeline-issue-01.png [ 35962 ] | |
Attachment | pipeline-issue-02.png [ 35963 ] |
Description |
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 |
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 EDIT: Attached are images of the configuration that I have set up for the pipeline. In 'branches to build' I have !pipeline-issue-01.png|thumbnail! !pipeline-issue-02.png|thumbnail! |
Attachment | pipeline-issue-01.png [ 35960 ] |
Attachment | pipeline-issue-02.png [ 35961 ] |
Description |
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 EDIT: Attached are images of the configuration that I have set up for the pipeline. In 'branches to build' I have !pipeline-issue-01.png|thumbnail! !pipeline-issue-02.png|thumbnail! |
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 EDIT: Attached are images of the configuration that I have set up for the pipeline. In 'branches to build' I have |
Description |
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 EDIT: Attached are images of the configuration that I have set up for the pipeline. In 'branches to build' I have |
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 EDIT: 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 !Single git push triggers all projects watching the repo.png|thumbnail! 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. |
Attachment | polling-ignores-fail.png [ 35964 ] |
Description |
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 EDIT: 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 !Single git push triggers all projects watching the repo.png|thumbnail! 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. |
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 EDIT: 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 !Single git push triggers all projects watching the repo.png|thumbnail! 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. !polling-ignores-fail.png|thumbnail! |
Description |
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 EDIT: 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 !Single git push triggers all projects watching the repo.png|thumbnail! 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. !polling-ignores-fail.png|thumbnail! |
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 !Single git push triggers all projects watching the repo.png|thumbnail! 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. !polling-ignores-fail.png|thumbnail! The problem with 'polling ignores commits..', I believe, may be related to this issue. |
Description |
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 !Single git push triggers all projects watching the repo.png|thumbnail! 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. !polling-ignores-fail.png|thumbnail! The problem with 'polling ignores commits..', I believe, may be related to this issue. |
Attached are images of the configuration that I have set up for the pipeline. !pipeline-issue-01.png|thumbnail! !pipeline-issue-02.png|thumbnail! 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 !Single git push triggers all projects watching the repo.png|thumbnail! 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. !polling-ignores-fail.png|thumbnail! The problem with 'polling ignores commits..', I believe, may be related to this issue. |
Assignee | Mark Waite [ markewaite ] |
Assignee | Mark Waite [ markewaite ] |
Attachment | github branch source.png [ 36032 ] |
Attachment | Screen Shot 2017-02-17 at 12.31.51.png [ 36035 ] |
Attachment | Screenshot from 2017-02-17 13-02-25.png [ 36040 ] |
Comment |
[ I give up. I am now using Multibranch Pipeline with *Git* under *Branch Sources* + *Periodically if not otherwise run*(1 minute interval) under *Build Triggers*. I think it's a horrible solution compared to my previous setup in a standalone pipeline (which worked 100% before Feb 10th) which built per github hook request whenever someone pushes to the repo, unlike multibranch pipeline which only works though a periodic poll ] |
Component/s | github-plugin [ 15896 ] | |
Component/s | git-plugin [ 15543 ] |
Resolution | Not A Defect [ 7 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
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.