![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
jenkins-jira-issue-updater |
|
Created:
|
29/Jan/14 10:05 PM
|
|
Description:
|
Whenever we create a new build we have to enable additional behaviors and force a wipe out of the workspace and a new clone.
Why does the GIT plugin do a 'git fetch' by default if it doesn't merge in the changes from origin? It just seems it would make sense if by default it did a git pull
|
|
Fix Versions:
|
current |
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Matt Evans
|
|
|
|
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.
