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

[f...@wizcorp.jp (JIRA)]

Frank Lee commented on JENKINS-23415 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading Thank you for the quick reply! Sorry, the branches in my original post with the last "git checkout" and "git pull" was wrong. I've corrected the branches above. It's pulling the "develop" branch into "test/branch1". Then pulling "test/branch1" into "test/branch2". Could you try that to see if it's reproducible? Not sure if it makes a difference, but instead of polling, I'm using githhub-webhook on the Github repo. So pushes to the Github repo triggers Github to send payloads to the Jenkins server. Details on the configuration of the job for branch1 are: "Discard Old Builds" is checked "Max # of builds to keep" is set to 50 "Enable project-based security" is set. "GitHub project" is set with the URL of the github repo. "HipChat Notifications" is set with the Project Room. "Restrict where this project can be run" is set with "Label _expression_" set to "master". "Source Code Management" is set with "Git" selected. In that section the following are set: "Repository URL" has the ssh URL from Github. "Credentials" is set to none. "Branch Specifier" is set to "origin/test/branch1" "Additional Behaviours" has "Advanced sub-modules behaviours" set with "Disable submodules processing" checked. "Build Triggers" has "Build when a change is pushed to GitHub" checked. "Build Environment" has "Delete workspace before build starts" and "Color ANSI Console Output" both checked. "Build" has "Execute shell" with a shell script to do stuff for branch1. The "Post-build Actions" has HipChat and email notification. Details for the job for branch2 are the exact same, except for: "Branch Specifier" is set to "origin/test/branch2" To add, originally, we wanted only 1 job by using regex as follows: "Branch Specifier" is set to "origin/test/**" And in the "Execute shell" have "if GIT_BRANCH=branch1 then do... if GIT_BRANCH=branch2 then do ...", which is more maintainable than maintaining multiple Jenkins jobs. But with the 1 job with the regex, we're having the opposite problem. Instead of the job triggers an extra build, it's ignores subsequent triggers when the first build is running. So for example: when we push 2 or more times immediately while the job is running from the first push that triggered it, consecutive jobs won't queue up. The jenkins.log does show Jenkins receiving the webhook and poking the job, but the job just doesn't trigger. This is a separate problem, but I mention it because it may have some relationship to the original problem. I'll try duplicating it in a test environment. And try testing 1.9.1.

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.