To reproduce:

1. Install and configure scm-sync-configuration to use Subversion.

• In my case, I was using a file:///... repo

2. Rename a job (configure job, change Project name).

Expected result:
Job is moved in Subversion repository.

Actual result:
1. scm-sync-configuration.fail.log: "Error while checking in file to scm repository"
2. Nothing happens in Subversion repository.
3. Any changes after this are queued up but never checked in.

Workaround:
Use git rather than svn. When using git as a backend, the plugin behaves as expected. Or if you need svn, the workaround is to make sure to never rename jobs.