[JENKINS-36836] Git path polling ignores do not work in Pipeline jobs - Jenkins Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Duplicate
Component/s: git-plugin, multi-branch-project-plugin (not Pipeline)
Labels:
Environment:
Jenkins LTS 2.7.1
Ubuntu 12.04
Git Plugin 2.5.2
Pipeline Plugin 2.2

Similar Issues:

Show

Description

Multibranch pipeline jobs seem to ignore git path polling rules when attempting to detect indexing changes and schedule builds.

More specifically:

I am using a "Periodically if not otherwise run" build trigger
I tested "Git polling ignores commits in certain paths" with the following:

1) Only including paths that I care about:
Included:
that-path-I-care-about/.*
Excluded:
(empty)

2) Including paths I care about and excluding a specific path:
Included:
that-path-I-care-about/.*
Excluded:
that-path-I-want-to-ignore/.*

3) Just using excluded paths:
Included:
(empty)
Excluded:
that-path-I-want-to-ignore/.*

None of them work as expected. Builds are triggered anytime a change is committed to the repo.

Attachments

Issue Links

duplicates

JENKINS-36195 Pipeline polling ignores special polling rules

Open

links to

CloudBees Internal OSS-1409

Activity

Ascending order - Click to sort in descending order

Preston Jennings created issue - 2016-07-20 21:26

Preston Jennings made changes - 2016-07-20 21:30

Field	Original Value	New Value
Description	Multibranch pipeline jobs seem to ignore git polling rules when attempting to detect indexing changes and scheduling builds. More specifically: - I am using a "Periodically if not otherwise run" build trigger - I tested "Git polling ignores commits in certain paths" with the following: 1) Only including paths that I care about: Included: that-path-I-care-about/.* Excluded: (empty) 2) Including paths I care about and excluding a specific path: Included: that-path-I-care-about/.* Excluded: that-path-I-want-to-ignore/.* 3) Just using excluded paths: Included: (empty) Excluded: that-path-I-want-to-ignore/.* None of them work as expected. Builds are triggered anytime a change is committed to the repo.	Multibranch pipeline jobs seem to ignore git polling rules when attempting to detect indexing changes and schedule builds. More specifically: - I am using a "Periodically if not otherwise run" build trigger - I tested "Git polling ignores commits in certain paths" with the following: 1) Only including paths that I care about: Included: that-path-I-care-about/.* Excluded: (empty) 2) Including paths I care about and excluding a specific path: Included: that-path-I-care-about/.* Excluded: that-path-I-want-to-ignore/.* 3) Just using excluded paths: Included: (empty) Excluded: that-path-I-want-to-ignore/.* None of them work as expected. Builds are triggered anytime a change is committed to the repo.

Preston Jennings made changes - 2016-07-20 21:30

Summary

Git polling ignores do not work in Multibranch Pipeline job

Git path polling ignores do not work in Multibranch Pipeline job

Preston Jennings made changes - 2016-07-20 21:30

Description

Multibranch pipeline jobs seem to ignore git polling rules when attempting to detect indexing changes and schedule builds.

More specifically:
- I am using a "Periodically if not otherwise run" build trigger
- I tested "Git polling ignores commits in certain paths" with the following:

1) Only including paths that I care about:
Included:
that-path-I-care-about/.*
Excluded:
(empty)

2) Including paths I care about and excluding a specific path:
Included:
that-path-I-care-about/.*
Excluded:
that-path-I-want-to-ignore/.*

3) Just using excluded paths:
Included:
(empty)
Excluded:
that-path-I-want-to-ignore/.*

None of them work as expected. Builds are triggered anytime a change is committed to the repo.

Multibranch pipeline jobs seem to ignore git path polling rules when attempting to detect indexing changes and schedule builds.

More specifically:
- I am using a "Periodically if not otherwise run" build trigger
- I tested "Git polling ignores commits in certain paths" with the following:

1) Only including paths that I care about:
Included:
that-path-I-care-about/.*
Excluded:
(empty)

2) Including paths I care about and excluding a specific path:
Included:
that-path-I-care-about/.*
Excluded:
that-path-I-want-to-ignore/.*

3) Just using excluded paths:
Included:
(empty)
Excluded:
that-path-I-want-to-ignore/.*

None of them work as expected. Builds are triggered anytime a change is committed to the repo.

Mark Waite made changes - 2016-07-21 01:33

Assignee

Mark Waite [ markewaite ]

mcrooney made changes - 2016-07-22 19:05

Summary

Git path polling ignores do not work in Multibranch Pipeline job

Git path polling ignores do not work in Pipeline jobs

mcrooney added a comment - 2016-07-22 19:07

Seeing this as well on a normal pipeline job, so I don't believe it is specific to multibranch ones. Perhaps the issue has something to do with the way workspaces are handled for Pipeline jobs? I posted about it here: https://groups.google.com/forum/#!msg/jenkinsci-users/wNIMGhJ76rA/HddRoHW-CAAJ

mcrooney added a comment - 2016-07-22 19:07 Seeing this as well on a normal pipeline job, so I don't believe it is specific to multibranch ones. Perhaps the issue has something to do with the way workspaces are handled for Pipeline jobs? I posted about it here: https://groups.google.com/forum/#!msg/jenkinsci-users/wNIMGhJ76rA/HddRoHW-CAAJ

R. Tyler Croy made changes - 2016-07-25 23:52

Workflow

JNJira [ 173579 ]

JNJira + In-Review [ 185209 ]

Jesse Glick added a comment - 2016-08-29 23:00

Sounds like a duplicate.

Jesse Glick added a comment - 2016-08-29 23:00 Sounds like a duplicate.

Jesse Glick made changes - 2016-08-29 23:00

Link

This issue duplicates JENKINS-36195 [ JENKINS-36195 ]

Jesse Glick made changes - 2016-08-29 23:00

Resolution		Duplicate [ 3 ]
Status	Open [ 1 ]	Resolved [ 5 ]

mcrooney added a comment - 2016-08-30 17:38

jglick, are you sure this is a duplicate of that issue? That issue appears to be for ignores defined in a Jenkinsfile itself, and in that issue the author of this issue chimes in, and is told it is a different issue, so he says he will create a different one and links this issue. See https://issues.jenkins-ci.org/browse/JENKINS-36195?focusedCommentId=264748&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-264748. I'm going to unmark it as a duplicate to save you time, but if I'm wrong feel free to re-mark it and accept my apologies

mcrooney added a comment - 2016-08-30 17:38 jglick , are you sure this is a duplicate of that issue? That issue appears to be for ignores defined in a Jenkinsfile itself, and in that issue the author of this issue chimes in, and is told it is a different issue, so he says he will create a different one and links this issue. See https://issues.jenkins-ci.org/browse/JENKINS-36195?focusedCommentId=264748&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-264748 . I'm going to unmark it as a duplicate to save you time, but if I'm wrong feel free to re-mark it and accept my apologies

mcrooney made changes - 2016-08-30 17:38

Resolution	Duplicate [ 3 ]
Status	Resolved [ 5 ]	Reopened [ 4 ]

S D added a comment - 2016-09-27 12:08

+1, polling rules do not work for simple pipeline & multi-branch pipeline jobs. In my case I'm trying to ignores commits from certain users.

S D added a comment - 2016-09-27 12:08 +1, polling rules do not work for simple pipeline & multi-branch pipeline jobs. In my case I'm trying to ignores commits from certain users.

Slawomir Demichowicz added a comment - 2016-10-10 14:01

Same issue here. Ignoring commits messages does not work with multibranch pipeline.

Slawomir Demichowicz added a comment - 2016-10-10 14:01 Same issue here. Ignoring commits messages does not work with multibranch pipeline.

Gleb Samsonov added a comment - 2016-12-15 16:43

for me, it looks like all include/exclude rules don't work properly if we'll use jobs without the persistent workspace (any pipeline-jobs for example). It caused by a git-plugin code (https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java). This plugin tries to find a workspace for polling and if this workspace doesn't exist - it compares revision hashes from the latest build and from actual repo (`git ls-remote -h`) . And obviously if we've updated repo these hashes differ so new build is starting

Gleb Samsonov added a comment - 2016-12-15 16:43 for me, it looks like all include/exclude rules don't work properly if we'll use jobs without the persistent workspace (any pipeline-jobs for example). It caused by a git-plugin code ( https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java ). This plugin tries to find a workspace for polling and if this workspace doesn't exist - it compares revision hashes from the latest build and from actual repo (`git ls-remote -h`) . And obviously if we've updated repo these hashes differ so new build is starting

Alexander Vorobiev added a comment - 2016-12-26 09:05

Can this functionality be moved to later stages?
So the repository is still fetched, but some steps can be skipped in case there are no appropriate changes as described in ~~JENKINS-37978~~.

Alexander Vorobiev added a comment - 2016-12-26 09:05 Can this functionality be moved to later stages? So the repository is still fetched, but some steps can be skipped in case there are no appropriate changes as described in JENKINS-37978 .

Michael Andrews added a comment - 2017-02-08 15:19

Path inclusions and exclusions (in a NON-MULTIBRANCH project) seem to work fine when there is a persistent workspace (we use the master to Checkout all code - then move on to a worker node). This is the case in NON-PIPELINE jobs as well and has been as such for some time. The USER inclusion/exclusion do not work in pipelines. Definitely Hoping for a fix to the user exclusions soon as our automated tagging and version bumping always results in a new build.

Michael Andrews added a comment - 2017-02-08 15:19 Path inclusions and exclusions (in a NON-MULTIBRANCH project) seem to work fine when there is a persistent workspace (we use the master to Checkout all code - then move on to a worker node). This is the case in NON-PIPELINE jobs as well and has been as such for some time. The USER inclusion/exclusion do not work in pipelines. Definitely Hoping for a fix to the user exclusions soon as our automated tagging and version bumping always results in a new build.

Janusz Jaworski made changes - 2017-02-14 11:47

Comment

[ Maybe this bug is connected with file https://github.com/jenkinsci/workflow-job-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java: line 547 method @Override public PollingResult poll(TaskListener listener). I didn't find any git extensions and checks that should ignore commits. ]

Jesse Glick added a comment - 2017-02-15 16:35

It is well known that you cannot use path exclusions when Git is configured to perform master-based polling, due to limitations in the Git network protocol. Would be solvable only by using a master repo cache the way the Mercurial plugin does, and in fact git already does for multibranch projects. I think this is already filed somewhere.

Polling exclusions are not currently supported for multibranch projects under any circumstances. That is probably also already filed somewhere.

Jesse Glick added a comment - 2017-02-15 16:35 It is well known that you cannot use path exclusions when Git is configured to perform master-based polling, due to limitations in the Git network protocol. Would be solvable only by using a master repo cache the way the Mercurial plugin does, and in fact git already does for multibranch projects. I think this is already filed somewhere. Polling exclusions are not currently supported for multibranch projects under any circumstances. That is probably also already filed somewhere.

Stephen Connolly made changes - 2017-02-24 12:53

Resolution		Duplicate [ 3 ]
Status	Reopened [ 4 ]	Closed [ 6 ]

Michael Andrews added a comment - 2017-02-24 15:15

User exclusions are now working. This is from one of our pipelines:

Ignored commit 73adf973ee91ff5b21c0638878eee33df7204544: Found excluded author: Jenkins

Michael Andrews added a comment - 2017-02-24 15:15 User exclusions are now working. This is from one of our pipelines: Ignored commit 73adf973ee91ff5b21c0638878eee33df7204544: Found excluded author: Jenkins

Ron Swanson added a comment - 2017-02-24 19:27

killdash9 Good day. Can you please say more about how you got that working?

Ron Swanson added a comment - 2017-02-24 19:27 killdash9 Good day. Can you please say more about how you got that working?

Maxfield Stewart added a comment - 2017-04-20 04:32

killdash9 I can get those log messages, however in situations where there is no actual workspace on a build node it still triggers the build (even though there's a duplicate workspace on the Jenkins master server). So I believe it works but still doesn't recognize using the master servers local copy as the source to make the determination. Which is not ideal.

Maxfield Stewart added a comment - 2017-04-20 04:32 killdash9 I can get those log messages, however in situations where there is no actual workspace on a build node it still triggers the build (even though there's a duplicate workspace on the Jenkins master server). So I believe it works but still doesn't recognize using the master servers local copy as the source to make the determination. Which is not ideal.

CloudBees Inc. made changes - 2017-12-05 05:45

Remote Link

This issue links to "CloudBees Internal OSS-1409 (Web Link)" [ 18707 ]

Venkatesh added a comment - 2021-02-15 11:04

Can anyone please confirm if this is working for Multibranch Pipeline jobs? Also, please provide some syntax. It's a humble request.

Venkatesh added a comment - 2021-02-15 11:04 Can anyone please confirm if this is working for Multibranch Pipeline jobs? Also, please provide some syntax. It's a humble request.

People

Assignee:: Unassigned

Reporter:: Preston Jennings

Votes:: 21 Vote for this issue

Watchers:: 35 Start watching this issue

Dates

Created:: 2016-07-20 21:26

Updated:: 2021-02-15 11:04

Resolved:: 2017-02-24 12:53