-
Bug
-
Resolution: Unresolved
-
Minor
-
None
I'm using two Jenkinsfiles to describe similar pipelines, e.g.
- //streamProject/components/A/Jenkins/Jenkinsfile.release
- //streamProject/components/A/Jenkins/Jenkinsfile.coverage
The first one is a normal release pipeline which gets triggered by Perforce changes.
The second one is scheduled to run once daily.
Now I do not want the first pipeline to start if the second pipeline script is changed. Therefore I have the following inside Jenkinsfile.release:
checkout([$class: 'PerforceScm', credential: 'p4user', filter: [[$class: 'FilterPathImpl', path: '//streamProject/components/A/.p4ignore.txt'], [$class: 'FilterPathImpl', path: '//streamProject/components/A/Jenkins/Jenkinsfile.coverage']], populate: [$class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [enable: false], pin: '', quiet: true, replace: true], workspace: [$class: 'StreamWorkspaceImpl', charset: 'none', format: 'jenkins_${NODE_NAME}_${JOB_NAME}', pinHost: false, streamName: '//streamProject'] ] )
So changes to Jenkinsfile.coverage should not lead to a new build of the job that is based on Jenkinsfile.release. But it did.
I'm just not sure whether there is some misunderstanding on my side regarding how that filter feature shall work.