hi,

so I have installed scm sync plugin and configure it to work with svn.
Now things go ok as long as we do changes to existing configuration.
However every time we remove a job manual intervention is necessary.
In the scm sync log I see a sequence of:
- change existing
- change existing
- add new
- delete old
- severe error - can not delete - resource out of sync

At this moment I drop to cli, and have to do 'svn up' in
scm-sync-configuration/checkoutConfiguration.
Sometimes it is fine, and next change continue magically, sometimes I have
to do 'svn clean', 'svn up'.

Should content of scm-sync-configuration/checkoutConfiguration be always in
sync with latest version of repo?
In my case I observe, that plugin it doesn't do it.
Can it be, that I am missing something in configuration?

In case of rename, there is another annoyance on top of the one I already
described. The folder with a job has more than config.xml in it
(nextBuildNumber scm-polling.log svnexternals.txt builds). Extra files end
up in repo, directory (file) is hanging around market with (?).

I have an option to switch to git. Has anyone better experience using git
as repo for svm sync?

Thanks in advance,
Pawel

Reply via email to