|
||||||||
|
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/d/optout.
Daniel Beck sorry to be a pest here. Any idea when the remaining issue you noted might be fixed? I'm wondering if I need to build my own hybrid of 2.3 +
JENKINS-18534. We have a release coming up and I don't want management to run into this issue when building off our release branch. I've not built a Jenkins plugin before so it will be a challenge, but I don't want to rollback the time consuming changes I made when we moved to the 2.4.1 plugin to getJENKINS-18534.