We've got some Pipeline jobs that are using "Polling ignores commits in certain paths", plus the required "Force polling using workspace" option.
It looks like we've got this set up correctly based on documentation and seeing this in the polling log: "Ignored commit 742b406b1d31bc04cff22c463561b381af0377fc: Found only excluded paths: " However, then it seems to build it anyway. I'm wondering if this has something to do with how Pipeline jobs don't seem to have a direct workspace for the whole thing?
Polling for changes in
> git rev-parse origin/master^{commit} # timeout=10
> git log --full-history --no-abbrev --format=raw -M -m --raw acde0988ce12d03c232baab96b0ca0fcd5c268fb..742b406b1d31bc04cff22c463561b381af0377fc # timeout=10
Ignored commit 742b406b1d31bc04cff22c463561b381af0377fc: Found only excluded paths:
Using strategy: Default
[poll] Last Built Revision: Revision acde0988ce12d03c232baab96b0ca0fcd5c268fb (origin/master)
using .gitcredentials to set credentials
> git --version # timeout=10
> git init /var/cache/tomcat8/temp/hudson7613875610483359225tmp # timeout=10
> git config --local credential.username redacted # timeout=10
> git config --local credential.helper store --file=/var/cache/tomcat8/temp/git7992680616771925108.credentials # timeout=10
> git config --local --remove-section credential # timeout=10
[poll] Latest remote head revision on refs/heads/master is: 742b406b1d31bc04cff22c463561b381af0377fc
Done. Took 1.6 sec
Changes found