[
https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-23091:
------------------------------------
Job now tells user via email to run using github::JIRA mappings...
{code}
./util/getProjectRootPomParents.sh -updateRootPom -createBranch -b jbosstools-4.4.2.x -b2
master -pv 4.4.2.Final-SNAPSHOT -w1 /tmp/jbt.github -vjbt 4.4.2.Final -vds 10.2.0.GA
-tpmin 4.60.1.Final -tpmax 4.60.1.Final -jirahost
https://issues.stage.jboss.org -jirauser
jiralint -jirapwd drauc3er -p1 "aerogear::aerogear-hybrid arquillian base::foundation
browsersim central forge freemarker hibernate javaee::jsf jst livereload openshift server
vpe::visual-page-editor-core webservices webservices integration-tests" -p2
"build build-sites::updatesite discovery::central-update devdoc
download.jboss.org
maven-plugins:build versionwatch" -p3 "artwork ci::build devdoc
product::installer qa website"
{code}
... and you end up with this a commit message containing a JIRA ID, #comment, and #close:
{code}
# >>> jbosstools-integration-tests <<<
# Commit change to
https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po...
pushd /tmp/jbt.github/jbosstools-integration-tests >/dev/null && perl -0777
-i.orig -pe \
's#(<artifactId>parent</artifactId>)[\r\n\
\t]+(<version>)([\d.]+[^<>]+)(</version>)#\1\n\t\t<version>'4.4.2.Final-SNAPSHOT'\4#igs'
\
pom.xml && git commit -m "JBIDE-22819 #comment bump up to parent pom version
= 4.4.2.Final-SNAPSHOT #close" . && git push origin master &&
popd >/dev/null; echo ">>>
https://github.com/jbosstools/jbosstools-integration-tests/commits/master...
# >>> jbdevstudio-product <<<
# Commit change to
https://github.com/jbdevstudio/jbdevstudio-product/blob/master/pom.xml
pushd /tmp/jbt.github/jbdevstudio-product >/dev/null && perl -0777 -i.orig -pe
\
's#(<artifactId>parent</artifactId>)[\r\n\
\t]+(<version>)([\d.]+[^<>]+)(</version>)#\1\n\t\t<version>'4.4.2.Final-SNAPSHOT'\4#igs'
\
pom.xml && git commit -m "JBDS-3955 #comment bump up to parent pom version =
4.4.2.Final-SNAPSHOT #close" . && git push origin master &&
popd >/dev/null; echo ">>>
https://github.com/jbdevstudio/jbdevstudio-product/commits/master"
{code}
I also created a pair of new components in JBIDE/JBDS called "integration-tests"
since there was no obvious place to map jbosstools-integration-tests in github to a
matching component in JIRA. [~mmalina] is the new component's owner/default assignee.
use #close smart tag in task JIRA commit messages
(getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are
applied
---------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-23091
URL:
https://issues.jboss.org/browse/JBIDE-23091
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: build
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.4.2.AM2
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)