uded created JENKINS-13773:
------------------------------
Summary: Perform Jira release based on user action or certain
plugin usage - Maven
Key: JENKINS-13773
URL: https://issues.jenkins-ci.org/browse/JENKINS-13773
Project: Jenkins
Issue Type: Improvement
Components: jira
Reporter: uded
It would be better for those of us that use Maven to drive the Jira version
release process differently. Currently, if I am doing a build based on Maven in
the project that uses most of the Jira plugin features (Generate Release Notes,
Mark a JIRA version as Released, Move issues...) it will execute those steps
for every build. That's not the case if you are using Maven Release plugin -
then the normal builds should not touch the JIRA release/changelog/etc. parts
unless one is actually doing the release!
I see three different solutions for this case:
1. Add a link in the project (better yet - in a build!) toolbar to perform a
release of JIRA version for the project manually. The screen can ask user about
the version to release.
2. Add a tight integration to [M2 Release
Plugin|https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin] and other
release plugins - but that seems to be somewhat hard to do.
3. Provide an extension point to trigger the release process and let other
plugins authors (like [M2 Release
Plugin|https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin]) use it.
Of course all three solutions (better 1+2) can be implemented for greater
usability.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
