[JIRA] (JENKINS-39768) Multiple checkout in Pipeline but only one seen in git data

[roidelapluie@inuits.eu (JIRA)]

Julien Pivotto created an issue

Jenkins / JENKINS-39768 Multiple checkout in Pipeline but only one seen in git data Issue Type: Bug Assignee: Mark Waite Attachments: multiscm3.png, multiscm4.png, multiscm5.png Components: git-plugin, pipeline, workflow-scm-step-plugin Created: 2016/Nov/16 8:14 AM Priority: Major Reporter: Julien Pivotto When using multiple SCM, only one is seen in "git data"; only one is seen in the pipeline stage view as well. See screenshots. Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[roidelapluie@inuits.eu (JIRA)]

Julien Pivotto commented on JENKINS-39768

Re: Multiple checkout in Pipeline but only one seen in git data There shoild be commits in all the builds; only 9.2-jenkins2-177 has commits in the first repo. Other build have commits in other repositories; that is not shown. Shows that we have multiple repositories. Clicking on any repo points to that page. Always about the first repo.

Add Comment

[roidelapluie@inuits.eu (JIRA)]

Julien Pivotto edited a comment on JENKINS-39768

Re: Multiple checkout in Pipeline but only one seen in git data

!multiscm3.png|thumbnail! There shoild should be commits in all the builds; only 9.2-jenkins2-177 has commits in the first repo. Other build have commits in other repositories; that is not shown. !multiscm4.png|thumbnail! Shows that we have multiple repositories. !multiscm5.png|thumbnail! Clicking on any repo points to that page. Always about the first repo.

Add Comment

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

Mark Waite assigned an issue to Unassigned

Jenkins / JENKINS-39768

Multiple checkout in Pipeline but only one seen in git data

Change By: Mark Waite Assignee: Mark Waite

Add Comment

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

Mark Waite commented on JENKINS-39768

Re: Multiple checkout in Pipeline but only one seen in git data Please provide more detailed instructions that will allow others to duplicate the problem on a separate machine. The pictures are certainly helpful, but there are many ways that I could make mistakes or make poor guesses on how you arrived at those pictures. Best would be a pointer to a Dockerfile or a public Docker instance which will show the problem, since then that can be installed and run and used for diagnosis. If that's not feasible, then please provide a numbered series of steps which state how to recreate the problem.

Add Comment

[roidelapluie@inuits.eu (JIRA)]

Julien Pivotto commented on JENKINS-39768

Re: Multiple checkout in Pipeline but only one seen in git data

Shell script: cd /tmp; git init foo;(cd foo; touch a; git add a; git commit -m a); for i in 0; do cp -r foo foo$i;(cd foo$i; git commit --amend -m a); done Pipeline: stage('test'){ node { checkouts = [:] for (i=0; i<10; i++) { def x = i checkouts["foo${x}"] = { checkout([$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: "foo${x}"], [$class: 'ScmName', name: "foo${x}"]], submoduleCfg: [], userRemoteConfigs: [[url: "/tmp/foo${x}"]]]) } } parallel checkouts } }

Add Comment

[roidelapluie@inuits.eu (JIRA)]

Julien Pivotto edited a comment on JENKINS-39768

Re: Multiple checkout in Pipeline but only one seen in git data

Shell script: {code} cd /tmp; git init foo;(cd foo; touch a; git add a; git commit -m a); for i in $(seq 0 30) ; do cp -r foo foo$i;(cd foo$i; git commit --amend -m a); done {code} Pipeline: {code}

stage('test'){     node {         checkouts = [:]

for (i=0; i< 10 30 ; i++) {

def x = i             checkouts["foo${x}"] = {                 checkout([$class: 'GitSCM', branches: [[name: '*/master']],                 doGenerateSubmoduleConfigurations: false, extensions:                 [[$class: 'RelativeTargetDirectory', relativeTargetDir: "foo${x}"],                 [$class: 'ScmName', name: "foo${x}"]],                 submoduleCfg: [], userRemoteConfigs: [[url: "/tmp/foo${x}"]]])            }         }         parallel checkouts     } }

{code}

Add Comment

[roidelapluie@inuits.eu (JIRA)]

Julien Pivotto commented on JENKINS-39768

Re: Multiple checkout in Pipeline but only one seen in git data

Mark Waite here you go.

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick updated an issue

Jenkins / JENKINS-39768

Multiple checkout in Pipeline but only one seen in git data

Change By: Jesse Glick Component/s: pipeline Component/s: workflow-scm-step-plugin Labels: pipeline

Add Comment

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

Mark Waite updated JENKINS-39768

The Pipeline script as included in the bug report is performing checkout to the same directory multiple times. Thus, it looks (to me) like it is doing the same thing multiple times. If multiple checkouts are needed, then they need to be a separate directories using either the dir or ws pipeline steps.

Jenkins / JENKINS-39768 Multiple checkout in Pipeline but only one seen in git data

Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

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

Mark Waite updated JENKINS-39768

Jenkins / JENKINS-39768 Multiple checkout in Pipeline but only one seen in git data

Change By: Mark Waite Status: Fixed but Unreleased Closed

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)