[JIRA] [git] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading

[mark.earl.wa...@gmail.com (JIRA)]

Mark Waite commented on JENKINS-23415 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading I attempted to duplicate the bug and was unsuccessful. I'll need more information before further investigation is performed. I created an initial repository with the following structure of commits: * 3bcea79 (upstream/test/main, test/main) Adapt README for test/main branch | * b3b7c59 (upstream/test/branch2, test/branch2) Adapt README for test/branch2 |/ | * 4f038d3 (upstream/test/branch1, test/branch1) Adapt README for the test/branch1 branch |/ | * 5ccca9d (HEAD, upstream/develop, develop) Updated README for the develop branch |/ * ea8c87b (upstream/master, master) Add README I created a script in the parent directory as you listed. I created a Jenkins job monitoring upstream/test/branch1, polling every 2 minutes, confirmed it was checking out correct branch I created a Jenkins job monitoring upstream/test/branch2, polling every 2 minutes, confirmed it was checking out correct branch I ran the script with argument 1 I confirmed the Jenkins job on test/branch1 ran and the Jenkins job on test/branch2 did not run After that, I tried further by defining a hook in the git repo which caused the Jenkins jobs to poll each time there was a commit to the repo. The jobs when polled as a result of the hook also behaved as expected. The job monitoring test/branch1 ran each time there was a commit to test/branch1. The job monitoring test/branch2 did not run when there was a commit to test/branch1. Can you provide more details of your configuration (job definitions, etc.) and confirm that the same problem can be duplicated on another Jenkins server? Can you update your git client plugin from 1.9.0 to the currently released 1.9.1, in case there is some relevant difference between the version you're using and the version I'm using?

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.