-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 2.22, Subversion Plug-in 2.6, Random string parameter plugin 1.0
I have a job with a random string parameter using SVN. I copied that job. The new job kept queuing up new builds for every SCM poll even though no changes had been made to the repository. The output messages said:
Job console output:
No revision recorded for https://<myrepositoryhere> in the previous build
SVN polling log:
Workspace doesn't contain https://<myrepositoryhere>. Need a new build.
I removed the random string parameter from the new job and the problem disappeared.
What exactly is the bug here? Random string parameter is basically needed to queue up duplicate builds circumventing Jenkins' detection of 'identical' queue items. So it appears to be working as designed both with (random value) parameter, and without – assuming you poll so often that the SCM revisions in the previous build haven't yet been determined when the new build is queued.