|
||||||||
|
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.
It's quite debatable.
I've experienced this issue after the migration from 1.480.3 to 1.509.3.
The plugin has been decoupled from the core between these releases, but Jenkins has not installed/enabled the plugin correctly upon the upgrade.
In my case it was a bug... or something like that