-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins Version 2.32.1
AccuRev Plugin Version 0.7.9
"Filter for Poll SCM" detects changes on similarly named folders.
We have three folders in the root of the stream named "hi-lib", "hi-lib-dal", and "hi-lib-dal-mongo". The "Filter for Poll SCM" for each folder job is set as "hi-lib/", "hi-lib-dal/", and "hi-lib-dal-mongo/". This is because without the trailing forward-slash AccuRev Plugin Version 0.7.6 would detect changes in each job even if changes were only promoted to one folder - adding the forward-slash resolved that issue.
With AccuRev Plugin Version 0.7.9, after promoting a change to "hi-lib-dal-mongo", all three builds started for detected changes in all three folders even though only "hi-lib-dal-mongo" contained a promoted change.
It appears something changed in AccuRev Plugin Version 0.7.9 that broke the polling and filtering by folders by ignoring the forward-slash that denoted the end of the folder name. Is there another way I should qualify the "Filter for Poll SCM" value? Thanks.
- relates to
-
JENKINS-41102 Job "Changes" do not match "Filter for Poll SCM"
-
- Closed
-
-
JENKINS-42939 AccuRev plugin does not start job on detected changes
-
- Closed
-
will simple wildcard work?
so in your case it would be for each job. They can still be comma seperated if you need more filters
?
or perhaps targeting both main and test scope
Your welcome to take a look at the current implementation and come with a PR
https://github.com/jenkinsci/accurev-plugin/blob/master/src/main/java/hudson/plugins/accurev/CheckForChanges.java#L101
This is my current implementation of simple wildcard
https://github.com/casz/accurev-plugin/blob/master/src/main/java/hudson/plugins/accurev/CheckForChanges.java#L103