[JIRA] [git-plugin] (JENKINS-13086) Clone to directory named for repository

2 views
Skip to first unread message

lieven.cardoen@gmail.com (JIRA)

unread,
May 4, 2015, 10:02:02 AM5/4/15
to jenkinsc...@googlegroups.com
Lieven Cardoen commented on New Feature JENKINS-13086
 
Re: Clone to directory named for repository

Is there already a solution for this without using the multiple-SCM plugin?

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

sagayaraj.x.david@verizon.com (JIRA)

unread,
Jun 26, 2015, 6:35:03 AM6/26/15
to jenkinsc...@googlegroups.com

Doug and Mark are correct to add local directory as the name of the GIT repo itself. In fact, it would be nice have it configured in the global GIT configuration whether to checkout GIT into workspace or workspace\$

{GIT_REPO}

sagayaraj.x.david@verizon.com (JIRA)

unread,
Jun 26, 2015, 6:36:02 AM6/26/15
to jenkinsc...@googlegroups.com
Sagayaraj David edited a comment on New Feature JENKINS-13086

mwils2424@gmail.com (JIRA)

unread,
Oct 7, 2015, 3:50:03 PM10/7/15
to jenkinsc...@googlegroups.com

Agreed Sagayaraj David
Being unable to clone multiple repositories to distinct folders is causing me some serious pain. I realize that I can manually clone these repos using a shell call, but in doing that I lose pieces of the plugin's functionality that I really like.

paskas@gmail.com (JIRA)

unread,
Jun 9, 2016, 8:49:01 AM6/9/16
to jenkinsc...@googlegroups.com

With Multiple-SCM Jenkins doesn't show repo changes for each build, this part in the summary is always empty

jielpe-cblv38@protonmail.com (JIRA)

unread,
Aug 16, 2018, 12:06:03 PM8/16/18
to jenkinsc...@googlegroups.com

I do not use Mutliple SCM and I only have a unique git repository.
Nevertheless as a simple and dummy user I would have been glad if the git step behaved just like a git clone + git checkout (detached) command !

So, to be able to tell git to clone onto a directory named from the repository is (seems to me)  indeed a very good idea !!
Note that I loose some time before understanding why  changing from a shell step with git clone to a git step made the job failing !

Another very good idea would have been to describe the current and very strange behavior in the step reference documentation which is (IMHO) often very light.

 

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

nicolas.deloof@gmail.com (JIRA)

unread,
Apr 24, 2019, 10:27:49 AM4/24/19
to jenkinsc...@googlegroups.com
Nicolas De Loof assigned an issue to Unassigned
 
Jenkins / New Feature JENKINS-13086
Change By: Nicolas De Loof
Assignee: Nicolas De Loof
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

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

unread,
Jan 13, 2020, 7:27:06 PM1/13/20
to jenkinsc...@googlegroups.com
Mark Waite closed an issue as Won't Fix
 

Jenkins Pipeline allows checkout to user defined directory names and allows multiple repositories to be used in a single Jenkins job. This won't be implemented in the git plugin because it is already available in Jenkins Pipeline

Change By: Mark Waite
Status: Open Closed
Resolution: Won't Fix
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages