|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-16024) SCM Sync fails to ... [email protected] (JIRA)
- [JIRA] (JENKINS-16024) SCM Sync fail... [email protected] (JIRA)
- [JIRA] (JENKINS-16024) SCM Sync fail... [email protected] (JIRA)
- [JIRA] (JENKINS-16024) SCM Sync fail... [email protected] (JIRA)
- [JIRA] (JENKINS-16024) SCM Sync fail... [email protected] (JIRA)
- [JIRA] (JENKINS-16024) SCM Sync fail... [email protected] (JIRA)
- [JIRA] (JENKINS-16024) SCM Sync fail... [email protected] (JIRA)
- [JIRA] (JENKINS-16024) SCM Sync fail... [email protected] (JIRA)
- [JIRA] (JENKINS-16024) SCM Sync fail... [email protected] (JIRA)
- [JIRA] (JENKINS-16024) SCM Sync fail... [email protected] (JIRA)

I faced the same issue with Jenkins 1.492 and SCM sync 0.0.6.1. I tried various Git repositories, one even without any access control. And always got the error message "aborted (scm manipulator not settled !)". But after restarting Jenkins everything works fine. So simply:
--> aborted (scm manipulator not settled !)
--> Configurations synced to SCM