![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
scm-sync-configuration |
|
Created:
|
26/Sep/14 8:10 PM
|
|
Description:
|
When a jenkins instance is running with an active sync plugin there seems to be an issue when a job gets renamed.
Steps to reproduce
- Setup jenkins instance with active sync to a git repository
- ensure some builds have completed so that a workspace is available
- rename job which has a work space
Expected Result
- Old job is moved to new job in VCS
Actual
- Job is moved and workspace information is pushed to the repo
- This also include lastSuccessful references etc.
Impact
- Configuration repo grows to a massive size as binaries start to get synced up to git (~5GB) in our case.
Resolution in the event of issue
- create new repo
- clone old repo
- back up config files
- reset hard until the point before the rename
- dump your backed up config over the top of the config (brings you to your latest greatest)
- clean up any jobs that should be deleted
- set the new repo as your upstream, commit and push
- reload the config from the new repo
This has the drawback of losing history between when things went wrong and when you fixed
|
|
Environment:
|
Jenkins ver. 1.570
SCM Sync Configuration Plugin ver. 0.0.8
GIT client plugin ver. 1.10.2
GIT plugin ver. 2.2.6
|
|
Project:
|
Jenkins
|
|
Labels:
|
scm
configuration
sync
plugin
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Arran Bartish
|
|
|
|
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
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
