I've setup a test with a repository that has several branches. I created a freestyle jenkins job that uses Git SCM to checkout the repo. When I run this job, it shows the below and results in multiple executions of the job:
Multiple candidate revisions Scheduling another build to catch up with <job name> Checking out Revision <id> (<branch>) I created a pipeline job, basically the same. It uses checkout, $class GitSCM and no extensions. When I run this job, it shows the below and does not schedule additional executions of the job: Multiple candidate revisions Checking out Revision <id> (<branch>) This is with Jenkins 2.235.5 and git-plugin 4.4.4, but this behavior has been consistent for some time. Is this a bug or do I need to do something differently to get the pipeline script to schedule additional executions of the job when multiple candidate revisions are found? thanks Keith -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/748a80e8-38c5-41da-80ae-c3e8089fa20cn%40googlegroups.com.
