[JIRA] (JENKINS-38113) Multiple SCMs Git repositories checks out wrong SHA.

[joe.kenn...@s3group.com (JIRA)]

Title: Message Title

Joe Kennedy created an issue   Jenkins / JENKINS-38113 Multiple SCMs Git repositories checks out wrong SHA. Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin, git-plugin, multiple-scms-plugin Created: 2016/Sep/09 7:13 PM Environment: Jenkins Ver 1.638 Multiple SCMs Plugin Ver. 0.3 Git Plugin Ver. 2.2.1 Git Client Plugin Ver. 1.9.1 Priority: Major Reporter: Joe Kennedy In my Jenkins job, I need to build from 3 GIT repositories hence, I use the multiple SCMs plugin. For each repository, the Branch Specifier is a String Parameter defaulting to */master. Name and Refspec parameters under each repository are blank. All is fine (i.e. using the default) until I run a specific build with say a TAG or a SHA for any one of the repositories as the Branch Specifier. From that point forward, even though the Branch Specifier defaults back to */master, the same SHA is checked out every time. Initially the Additional Behaviour → Clean before checkout was selected. I changed this to Wipe out repository & force clone but to no avail. I also noticed previously that this messed up Poll SCM build trigger in that it caused a build to happen even though all the SHAs from the previous build were unchanged and we ended up having a build every hour 24 hours a day until Poll SCM was dropped. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.