|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Yes, seems to be . . . in fact today ran into this situation:
Production System . . . been working for a long time. We did an upgrade and decided we wanted to save configuration files in our get hub and so installed SCM Config plugin . . . we had not yet even configured that (that was planned for later after the release) . . . so as far as I know it was just sitting there idle.
Job that had been running forever with no changes started getting the error . . . I "fixed it" by disabling the SCM Config plugin.
FWIW: I would REALLY like to be able to run both plugins together.
Frank