Status: Open (View Workflow)
Environment:Jenkins ver 2.204.2
Manually setting a pipeline job to poll SCM is resulting in a build being triggered each and every time polling starts.
In reviewing logs, the only change I see is the TAG created by the build itself. No other commits are in place.
Typical pipeline configuration is to poll SCM for change, build component, TAG the commit of the successful build, and post step will deleteDir() after each build.
While a tag is not seen as a commit, it is clear that in GIT, a tag is given a unique hash.
I have tried ignoring commits by the build user, but since the tag is not a code change, this does not work.
I have tried ignoring commits with messages, but since the tag is not seen as a commit, this does not work.
I have tried using a REGEX to ignore tags, however I am getting errors with the regex and illegal characters, so this has not worked either.