![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Nicolas De Loof
|
|
Components:
|
git |
|
Created:
|
18/Jul/13 1:05 PM
|
|
Description:
|
As a new user to the GIT SCM, I was very surprised to find out that the default (empty) value for the Branches to Build parameter attempted to pull all branches in the repo and execute the build operation on them. As a SCM/Integration engineer with 10 years of industry experience, I can assure you this is not the correct default behavior. While I agree that GIT presents SCM tasks and process in a way that many previous industry leading SCM tools had not, it still makes no sense for most projects to attempt to build multiple branches. This is especially true when it comes to the fact that the plugin has no logical means of identifying any correlation between the branches. The resultant build is a combination of unknown source configurations...which can only lead to unknown deliverable configurations.
The default behavior should be to default to only building master branch as a empty REPO will have this branch always, unless the end user has renamed that branch. It is safe to assume if the end user has renamed that branch that they should be educated enough to specify the desired target branch to build within the plugin.
|
|
Due Date:
|
31/Oct/13 12:00 AM
|
|
Environment:
|
All platforms
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Phil Johnson
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
