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

"Polling ignores commits in certain paths" is missing under "Behaviours" on Git Source

      In Jenkins pipeline configuration, there are some behaviors missing under "Behaviours" on "Git" source (Eg: Build Initiation Extensions).

      According to this documentation, expecting to utilize "Polling ignores commits in certain paths" in the project. But blocked with missing behaviors under configuration as mentioned above. Used Git Plugin version is 5.0.2 .

      Could anyone please guide to understand why such behaviors are not exposed in pipeline configuration?

      Attached screenshots for better understanding...

          [JENKINS-72245] "Polling ignores commits in certain paths" is missing under "Behaviours" on Git Source

          Mark Waite added a comment - - edited

          The image in the documentation shows that the job is named "git-freestyle". That job name is intentional as a way of showing that is what is being illustrated in that section of the documentation. I'll need to improve the documentation to make it clear in the text that the option is not available for Pipeline jobs.

          Pipeline provides more general purpose ways to ignore commits on certain paths. A stackoverflow article provides one technique with the changeset directive.

          Mark Waite added a comment - - edited The image in the documentation shows that the job is named "git-freestyle". That job name is intentional as a way of showing that is what is being illustrated in that section of the documentation. I'll need to improve the documentation to make it clear in the text that the option is not available for Pipeline jobs. Pipeline provides more general purpose ways to ignore commits on certain paths. A stackoverflow article provides one technique with the changeset directive.

          Mark Waite added a comment -

          This won't be implemented in Pipelines because there is already a better way to do this in Pipeline

          Mark Waite added a comment - This won't be implemented in Pipelines because there is already a better way to do this in Pipeline

            Unassigned Unassigned
            rupee Rupeekshan
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: