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

Workflow Git configuration doesn't allow to exclude some users/comments/paths from polling

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I've tested this behavoiur in:

      • Simple workflow job: You can add an exclusion behaviour, but it's ignored
      • Multibranch: There's no exclusion option.
      • Github organization: There's no exclusion option.

      If your workflow is doing some commit/push, this is an important feature to prevent your jobs to produce an infinite building loop.

        Attachments

          Issue Links

            Activity

            Hide
            jglick Jesse Glick added a comment -

            Simple workflow job: You can add an exclusion behaviour, but it's ignored

            Sounds like it could be a bug. But I wonder how you could even hope to have this work, since IIRC the exclusion option only works when using workspace-based polling, which is inefficient and not currently supported by Workflow (cf. JENKINS-26138).

            Multibranch: There's no exclusion option.

            Generally GitSCMSource seems to lack support for extensions. Would be an RFE in git-plugin.

            Github organization: There's no exclusion option.

            RFE for github-branch-source, dependent on the previous RFE. (There is no way to configure per-repository SCM settings I am afraid.)

            Show
            jglick Jesse Glick added a comment - Simple workflow job: You can add an exclusion behaviour, but it's ignored Sounds like it could be a bug. But I wonder how you could even hope to have this work, since IIRC the exclusion option only works when using workspace-based polling, which is inefficient and not currently supported by Workflow (cf. JENKINS-26138 ). Multibranch: There's no exclusion option. Generally GitSCMSource seems to lack support for extensions. Would be an RFE in git-plugin . Github organization: There's no exclusion option. RFE for github-branch-source , dependent on the previous RFE. (There is no way to configure per-repository SCM settings I am afraid.)

              People

              • Assignee:
                Unassigned
                Reporter:
                sergiorc Sergio Roldan
              • Votes:
                2 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated: