]
Max Rydahl Andersen commented on JBIDE-22728:
---------------------------------------------
great idea about making PR's for these if that can be automated - but not seeing why
this should mean remove the jira creation. Without the jira its not possible to see if
anything outstanding.
Would it not be the optimal of making the PR's and have the jira link to those created
PR's.
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)