Details
-
Type:
New Feature
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Won't Fix
-
Component/s: github
-
Labels:None
-
Similar Issues:
Description
Given the amount of projects that are using Git these days, it is highly recommended to include Git as the default functionality in Jenkins as opposed to installing it as plugin.
Ditto for GitHub.
Attachments
Activity
This seems like a pretty basic and common functionality. There is already support for archaic source code control systems like CVS and SVN, and nothing for Git shows the age of the project.
Can you reclassify to the right category so that right people can look at it?
arungupta
added a comment - This seems like a pretty basic and common functionality. There is already support for archaic source code control systems like CVS and SVN, and nothing for Git shows the age of the project.
Can you reclassify to the right category so that right people can look at it? I am with Arun here. It seems reasonable to either distribute without any plugins or with some modern stack. First thing I do after downloading Jenkins (which I do a lot) is downloading Gradle, Git (and one additional plugin 
).
Having SVN bundled but keeping Git out seem strange.
jbaruch
added a comment - I am with Arun here. It seems reasonable to either distribute without any plugins or with some modern stack. First thing I do after downloading Jenkins (which I do a lot) is downloading Gradle, Git (and one additional plugin ).
Having SVN bundled but keeping Git out seem strange. Duplicates JENKINS-9598.
This doesn't belong in the INFRA project. We generally don't want to bundle plugins anyways