|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
We had the exact same issue and the steps in the earlier comment worked to get the plugin to run for us.
However the association between the job's SCM repository and the needed credentials is lost so we would have to reconfigure every single build job to use the correct credentials (which are correctly available from the dropdown list). Given the rather large number of jobs in our Jenkins I'd rather not have to do that manually so I reverted back to 1.54 for now.
Did you see the same Oliver, or should I treat this as a separate issue and open a separate ticket?