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

2 views
Skip to first unread message

joe.kennedy@s3group.com (JIRA)

unread,
Sep 9, 2016, 3:14:01 PM9/9/16
to jenkinsc...@googlegroups.com
Joe Kennedy created an issue
 
Jenkins / Bug JENKINS-38113
Multiple SCMs Git repositories checks out wrong SHA.
Issue Type: Bug 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 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 Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

mark.earl.waite@gmail.com (JIRA)

unread,
Sep 9, 2016, 3:43:02 PM9/9/16
to jenkinsc...@googlegroups.com
Mark Waite assigned an issue to Unassigned
Change By: Mark Waite
Assignee: Mark Waite

mark.earl.waite@gmail.com (JIRA)

unread,
Sep 9, 2016, 3:55:01 PM9/9/16
to jenkinsc...@googlegroups.com
Mark Waite commented on Bug JENKINS-38113
 
Re: Multiple SCMs Git repositories checks out wrong SHA.

The multiple SCM's plugin has a number of unfortunate interactions with the git plugin (and other SCM plugins). It is unlikely those issues will be fixed any time soon.

You may want to evaluate using a pipeline definition to checkout multiple repositories into a single workspace. I'm sure there are still issues in that workflow, but it is receiving much more attention than the multiple SCM plugin. Refer to the multiple SCMs section of the workflow scm step plugin README.

rodrigc@FreeBSD.org (JIRA)

unread,
Sep 15, 2016, 9:38:03 PM9/15/16
to jenkinsc...@googlegroups.com
Craig Rodrigues resolved as Won't Fix
 

Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms
https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin

Change By: Craig Rodrigues
Status: Open Resolved
Resolution: Won't Fix

mark.earl.waite@gmail.com (JIRA)

unread,
Oct 22, 2019, 9:26:04 PM10/22/19
to jenkinsc...@googlegroups.com
Mark Waite closed an issue as Won't Fix
Change By: Mark Waite
Status: Resolved Closed
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages