I tried a rename with 0.0.9 and it failed.

Dec 17, 2015 1:16:56 PM WARNING hudson.plugins.scm_sync_configuration.SCMManipulator addFile
[addFile] Error while adding file : Exception while executing SCM command.
Dec 17, 2015 1:16:56 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator checkinFiles
[checkinFiles] Error while checkin : Exception while executing SCM command.
Dec 17, 2015 1:16:56 PM SEVERE hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness processCommitsQueue
Error while processing commit queue : Error while checking in file to scm repository
Dec 17, 2015 1:17:00 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy
[deleteHierarchy] Problem during remove : The git command failed.

I see the following in checkoutConfiguration/

# git status
On branch master
Your branch is ahead of 'origin/master' by 10 commits.
  (use "git push" to publish your local commits)
Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

	renamed:    jobs/SQS Mertics/config.xml -> jobs/SQS Metrics/config.xml

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   config.xml

I don't know which config.xml failed to add.

I see the following repeating in the logs

Dec 17, 2015 1:37:00 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy
[deleteHierarchy] Problem during remove : The git command failed.
Dec 17, 2015 1:38:00 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy
[deleteHierarchy] Problem during remove : The git command failed.
Dec 17, 2015 1:38:01 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy
[deleteHierarchy] Problem during remove : The git command failed.

I manually fixed by:

ssh jenkins
sudo su jenkins -s /bin/bash
cd ~/scm-sync-configuration/checkoutConfiguration/
git status  # see untracked files
git add -a
git commit -a -m "manual commit due to failed rename"
git push origin master
# all good

Then restarting jenkins.

Please see my earlier comments; this is still not working for us.

Same as issue JENKINS-25786

Have exactly the same issue with 0.0.9

Looking forward to see https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/32 merged, which appear to contain the fixes.

Added related to JENKINS-26652 link.

We are having exactly the same issue with 0.0.10 and are thus sadly forced to NOT use this plugin which would be awesome if this would work.
As soon as there is a job renamed/deleted, the plugin stops working at all and does not add any xml file to its folder which would be synced, thus a manual git commit/push does not help.
As previously said, https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/32 seems to fix the issue. Please take a look at it.
Thanks and kind regards, Paul

I experience this issue intermittently on deletes, and this is the steps I do to resolve:

1. cd $JENKINS_HOME/scm-sync-configuration/checkoutConfiguration/
2. git status

Make sure the changes listed in git status make sense

3. If uncommitted files, git commit

4. git push

5. Clear the error message

6. Restart jenkins.  This is important, otherwise the error message will continue to pop up

Hi kylejw,

Your solution fix issue. I even create job that runs on master to fix it:

Jenkins Job Free type:

Restrict where this project can be run: master

Execute shell command: 

cd $JENKINS_HOME/scm-sync-configuration/checkoutConfiguration/

git status
git add .
git commit -m "Fix synchronisation" 
git push

The scm sync configuration plugin is deprecated. No further work is expected on the plugin.

Users of this plugin are encouraged to migrate their jobs to Pipeline Plugin, so that their jobs will be specified in pipeline code that can be checked into an SCM, all without using the SCM Sync configuration plugin.

Users of this plugin are also encouraged to use the Configuration as Code Plugin to specify the configuration of their Jenkins server in a file which can be checked into an SCM, all without using the SCM Sync configuration plugin.