[jbosstools-issues] [JBoss JIRA] (JBIDE-22728) 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

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272442#comment-13272442 ] 

Max Rydahl Andersen commented on JBIDE-22728:
---------------------------------------------

I did not respond or said anything about what number of jiras are created, I simply pointed out if you remove jira and only have PR's  you loose tracking easily what is left to do. 

Nothing else. My understanding was that updating parent pom's can't be done reliably for all repos, but if it can then sure by all means have less jiras, just not zero jiras.

btw. wether there is 1 or 17 jiras vs 1 person I think is rather irrelevant since you could use smart commit messages (https://confluence.atlassian.com/fisheye/using-smart-commits-298976812.html) and simply have "JBIDE-xyz #resolve" in the commit message and when the PR gets pushed the jira gets automatically resolved. Then you can could have lets say 13 of these go through easily and have 4 fail and it could be fix by one or more people.
Anyway - tons of flexiblity and automation in this.




> 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)