Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42020

branches to build specifier broken

    Details

    • 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

          ralphie02 Ralph A created issue -
          ralphie02 Ralph A made changes -
          Field Original Value New Value
          Attachment Screenshot from 2017-02-14 13-56-31.png [ 35949 ]
          ralphie02 Ralph A made changes -
          Attachment Screenshot from 2017-02-14 13-56-31.png [ 35949 ]
          ralphie02 Ralph A made changes -
          markewaite Mark Waite made changes -
          Assignee Mark Waite [ markewaite ]
          ralphie02 Ralph A made changes -
          Assignee Mark Waite [ markewaite ]
          ralphie02 Ralph A made changes -
          Assignee Mark Waite [ markewaite ]
          ralphie02 Ralph A made changes -
          Attachment pipeline-issue-01.png [ 35960 ]
          ralphie02 Ralph A made changes -
          Attachment pipeline-issue-02.png [ 35961 ]
          ralphie02 Ralph A made changes -
          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

          ralphie02 Ralph A made changes -
          Attachment pipeline-issue-01.png [ 35962 ]
          Attachment pipeline-issue-02.png [ 35963 ]
          ralphie02 Ralph A made changes -
          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!
          ralphie02 Ralph A made changes -
          Attachment pipeline-issue-01.png [ 35960 ]
          ralphie02 Ralph A made changes -
          Attachment pipeline-issue-02.png [ 35961 ]
          ralphie02 Ralph A made changes -
          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
          ralphie02 Ralph A made changes -
          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.
          ralphie02 Ralph A made changes -
          Attachment polling-ignores-fail.png [ 35964 ]
          ralphie02 Ralph A made changes -
          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!
          ralphie02 Ralph A made changes -
          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.
          ralphie02 Ralph A made changes -
          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.
          ralphie02 Ralph A made changes -
          Assignee Mark Waite [ markewaite ]
          markewaite Mark Waite made changes -
          Assignee Mark Waite [ markewaite ]
          ralphie02 Ralph A made changes -
          Attachment github branch source.png [ 36032 ]
          stephenconnolly Stephen Connolly made changes -
          ralphie02 Ralph A made changes -
          ralphie02 Ralph A made changes -
          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 ]
          thawkins83 T.J. Hawkins made changes -
          Component/s github-plugin [ 15896 ]
          Component/s git-plugin [ 15543 ]
          integer Kanstantsin Shautsou made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Not A Defect [ 7 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              ralphie02 Ralph A
            • Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: