-
Bug
-
Resolution: Won't Do
-
Minor
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...
- is duplicated by
-
-
- Closed
-
[JENKINS-72245] "Polling ignores commits in certain paths" is missing under "Behaviours" on Git Source
Rupeekshan
created issue -
Rupeekshan
made changes -
| Description |
Original:
h4. {color:#172b4d}In Jenkins pipeline configuration, there are some behaviors missing under "{*}Behaviours{*}" on "{*}Git{*}" source (Eg: Build Initiation Extensions). {color}
{color:#172b4d}According to [documentation|[https://plugins.jenkins.io/git/#plugin-content-build-initiation-extensions],] 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 .{color} {color:#172b4d}Could anyone please guide to understand why such behaviors are not exposed in pipeline configuration?{color} h4. {color:#172b4d}Attached screenshots for better understanding...{color} |
New:
h4. {color:#172b4d}In Jenkins pipeline configuration, there are some behaviors missing under "Behaviours" on "Git" source (Eg: Build Initiation Extensions). {color}
{color:#172b4d}According to this [documentation|#plugin-content-build-initiation-extensions],], 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 .{color} {color:#172b4d}Could anyone please guide to understand why such behaviors are not exposed in pipeline configuration?{color} h4. {color:#172b4d}Attached screenshots for better understanding...{color} |
| Assignee | Original: Mark Waite [ markewaite ] |
| Priority | Original: Blocker [ 1 ] | New: Minor [ 4 ] |
| Description |
Original:
h4. {color:#172b4d}In Jenkins pipeline configuration, there are some behaviors missing under "Behaviours" on "Git" source (Eg: Build Initiation Extensions). {color}
{color:#172b4d}According to this [documentation|#plugin-content-build-initiation-extensions],], 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 .{color} {color:#172b4d}Could anyone please guide to understand why such behaviors are not exposed in pipeline configuration?{color} h4. {color:#172b4d}Attached screenshots for better understanding...{color} |
New:
h4. {color:#172b4d}In Jenkins pipeline configuration, there are some behaviors missing under "Behaviours" on "Git" source (Eg: Build Initiation Extensions). {color}
{color:#172b4d}According to this [documentation|https://plugins.jenkins.io/git/#plugin-content-polling-ignores-commits-in-certain-paths], 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 .{color} {color:#172b4d}Could anyone please guide to understand why such behaviors are not exposed in pipeline configuration?{color} h4. {color:#172b4d}Attached screenshots for better understanding...{color} |
| Link |
New:
This issue is duplicated by |
This won't be implemented in Pipelines because there is already a better way to do this in Pipeline
| Resolution | New: Won't Do [ 10001 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
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.