|
||||||||
|
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.
I experienced this as well, both with the current code base as well as going back to the 1.3.3 time frame with 34c17d66dc3fae5cdd52efb387e4ae1e97a040d2. However, I found that if I removed the old plugin folder and the build-pipeline-plugin.jpi file, copied the new build-pipeline-plugin.hpi to the plugins folder, renamed as a jpi file. It deployed successfully. I don't know which of these steps were the 'fix'. Actually, this did not work for the current head.