[
https://issues.jboss.org/browse/JBIDE-22728?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-22728:
------------------------------------
If only one person is to be responsible for this root pom / branching process, you'd
like them to have to deal with 17 JIRAs and 17 PRs? Isn't that overkill when we could
JUST have 1 JIRA and 17 PRs, or even simpler, 1 email and 17 PRs?
[~akazakov] as the person who'll be running this, which would you prefer? Lots of Task
JIRAs + generated PRs? 1 JIRA + generated PRs? No JIRAs + generated PRs? Generated email
notification?
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)