|
||||||||
|
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)

Ok, it sounds weird to me![]()
You likely encounters these "scm manipulator not settled" when you can't authenticate against your repository.
Eventually, you could try to :
Here, the plugin will try to checkout things from repository url, and if it fails, it should log the reason why it failed.