Once a Jenkins job is renamed (or deleted) then the plugin generates SCM errors and does not commit anything to SVN:
SCM Sync status :
Thu Jun 01 09:35:42 BST 2017 : Delete jobs/My_Jenkins_Job/```
When I manually go to the plugin's directory ".jenkins/scm-sync-configuration/checkoutConfiguration/", and I run "svn status -q", I can see that the svn check out is at a wrong state:
D jobs/My_Jenkins_Job
D jobs/My_Jenkins_Job/config.xml
A jobs/My_Jenkins_Job_New_Name
A jobs/My_Jenkins_Job_New_Name/config.xml
I then try to manually commit the changes by doing:
svn commit -m "Commit current changes"
But I get:
svn: E155011: Commit failed (details follow):
svn: E155011: Directory '/svn/.jenkins/scm-sync-configuration/checkoutConfiguration/jobs/My_Jenkins_Job' is out of date
svn: E170004: Item '/svn/jobs/My_Jenkins_Job' is out of date
When I run:
svn update
I am able to manually commit.
However, the plugin continuous to generate the following error every time I modify any Jenkins job:
SCM Sync status :
Thu Jun 01 09:35:42 BST 2017 : Delete jobs/My_Jenkins_Job/
My current workaround is:
Update plugin's SVN check out
Manually commit any changes from the plugin's directory
Once a Jenkins job is renamed (or deleted) then the plugin generates SCM errors and does not commit anything to SVN:
When I manually go to the plugin's directory ".jenkins/scm-sync-configuration/checkoutConfiguration/", and I run "svn status -q", I can see that the svn check out is at a wrong state:
I then try to manually commit the changes by doing:
svn commit -m "Commit current changes"
But I get:
When I run:
svn update
I am able to manually commit.
However, the plugin continuous to generate the following error every time I modify any Jenkins job:
My current workaround is: