[
https://issues.jboss.org/browse/JBIDE-22728?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-22728:
------------------------------------
Having discussed this in more depth with Max last week, I'd like to try to implement
his idea of creating PRs w/ the "smart commit message" of "JBIDE-####
#close" so that as each PR is merged the 17 JIRAs would be closed automatically. That
would give us JIRAs to track the changes, AND reduce the overhead involved in managing
them.
However, I've tested smart commits with JBDS JIRAs and so far they've not worked.
[~maxandersen] do you know how to enable smart commits for JBDS JIRA? I'll do more
testing with JBIDE JIRA in the meantime, but since we need a JBDS JIRA created for
tracking root pom changes in devstudio, it would be great to use smart commits for that
one too.
Script the process for jbosstools projects to move up to the latest
parent pom in their root pom & all-tests pom; verify that changes are valid & push
to origin
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-22728
URL:
https://issues.jboss.org/browse/JBIDE-22728
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.4.1.AM1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.4.1.AM3
Current process for moving all the JBT projects to the latest parent pom involves
generating 15+ JIRAs assigned to the various project leads, so they can all adopt the
latest parent pom, verify their build works, and push the change.
With the advent of PR build jobs, we can now streamline this a little:
instead of creating Task JIRAs, create PRs & let them run automatically.
if they pass, push them in automatically (via script that Alexey or Denis would run)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)