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

Pipeline polling ignores special polling rules

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      The git plugin currently offers several special rules on polling:

      1. Polling ignores commits from certain users
      2. Polling ignores commits from certain paths (Included/Excluded regions)
      3. Polling ignores commits with certain messages
      4. Branch specifier

      For example:
      checkout([$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'UserExclusion', excludedUsers: 'dvader'], [$class: 'PathRestriction', excludedRegions: 'One/.*', includedRegions: 'Test/.*'], [$class: 'MessageExclusion', excludedMessage: '.\\[maven-release-plugin
      ].
      ']], gitTool: 'Default', submoduleCfg: [], userRemoteConfigs: [[credentialsId: '...', url: 'ssh://git@bitbucket.org/test.git']]])

      If a commit is committed to bitbucket.org/test.git, regardless of the user, location, branch or message, the step that includes the checkout will be run.

      Similar issue has been reported in:

        Attachments

          Issue Links

            Activity

            Hide
            schlitzered Stephan Schultchen added a comment -

            Mark Waite i am not using a Multibranch Pipeline, i am using a normal pipeline. and afaik this should work, it is just a bug, also normal pipeline jobs are not deprecated, so i do not see why i should switch.

             

            never the less, me and a colleague took a look at the problem, and we found the issue, and created a pull request & a another ticket:

            https://github.com/jenkinsci/git-plugin/pull/1046

            https://issues.jenkins.io/browse/JENKINS-64902

             

            so hopefully this issue will soon be fixed upstream

            Show
            schlitzered Stephan Schultchen added a comment - Mark Waite i am not using a Multibranch Pipeline, i am using a normal pipeline. and afaik this should work, it is just a bug, also normal pipeline jobs are not deprecated, so i do not see why i should switch.   never the less, me and a colleague took a look at the problem, and we found the issue, and created a pull request & a another ticket: https://github.com/jenkinsci/git-plugin/pull/1046 https://issues.jenkins.io/browse/JENKINS-64902   so hopefully this issue will soon be fixed upstream
            Hide
            markewaite Mark Waite added a comment -

            Stephan Schultchen I'm not aware of anyone intending to work on this issue. As far as I'm concerned, the git plugin should not apply its settings to pipeline polling because pipeline polling is handled in the branch API and by extensions of the branch API.

            If you use a multibranch pipeline, then you can limit which jobs are created through the basic branch build strategies plugin and can limit the paths with the pipeline multibranch build strategies plugin.

            Show
            markewaite Mark Waite added a comment - Stephan Schultchen I'm not aware of anyone intending to work on this issue. As far as I'm concerned, the git plugin should not apply its settings to pipeline polling because pipeline polling is handled in the branch API and by extensions of the branch API. If you use a multibranch pipeline, then you can limit which jobs are created through the basic branch build strategies plugin and can limit the paths with the pipeline multibranch build strategies plugin .
            Hide
            schlitzered Stephan Schultchen added a comment -

            the assigned user Kishore Babu Kavuru seems to have been inactive since november 2019. is there someone else who can pic up this issue?

            Show
            schlitzered Stephan Schultchen added a comment - the assigned user Kishore Babu Kavuru seems to have been inactive since november 2019. is there someone else who can pic up this issue?
            Hide
            androidk Andrii added a comment -

            +1, I have the same problem. Build of pipeline job is triggered despite of commit to path that specified in "Polling ignore commits in certain path" in job configuration (not inside Jenkinsfile)

             

            Show
            androidk Andrii added a comment - +1, I have the same problem. Build of pipeline job is triggered despite of commit to path that specified in "Polling ignore commits in certain path" in job configuration (not inside Jenkinsfile)  
            Hide
            carollyl Carol Lim added a comment - - edited

            Hi, does anyone able to get the excludedRegions and includedRegions to work in a pipeline job?

            Show
            carollyl Carol Lim added a comment - - edited Hi, does anyone able to get the excludedRegions and includedRegions to work in a pipeline job?

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              dvader Darth Vader
              Votes:
              104 Vote for this issue
              Watchers:
              106 Start watching this issue

                Dates

                Created:
                Updated: