[
https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-23091 at 9/21/16 3:45 PM:
-------------------------------------------------------------
For this to work, we will need to be able to run createTaskJIRAs.py 17 times (once per
project) and for each one, return the ID of the generated JIRA.
Then, we can use that JIRA number when calling getProjectRootPomParents.sh so that commit
comments when making changes look like this:
{code}
git commit -m \"JBIDE-23091 #close #comment bump up to parent pom version =
$\{version_parent}\"
{code}
instead of
{code}
git commit -m \"bump up to parent pom version = $\{version_parent}\"
{code}
was (Author: nickboldt):
For this to work, we will need to be able to run createTaskJIRAs.py 17 times (once per
project) and for each one, return the ID of the generated JIRA.
Then, we can use that JIRA number when calling getProjectRootPomParents.sh so that commit
comments when making changes look like this:
{code}
git commit -m \"JBIDE-23091 #close bump up to parent pom version =
$\{version_parent}\"
{code}
instead of
{code}
git commit -m \"bump up to parent pom version = $\{version_parent}\"
{code}
use #close smart tag in commit messages so JIRAs are closed
automatically
-------------------------------------------------------------------------
Key: JBIDE-23091
URL:
https://issues.jboss.org/browse/JBIDE-23091
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.4.2.AM1
Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs
that cause JIRA workflow to close JIRAs automatically
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)