[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

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-22728 at 8/19/16 9:09 PM:
-------------------------------------------------------------

PR to support fixing root poms and creating branches:

https://github.com/jbosstools/jbosstools-build-ci/pull/152/files

Sample run of getProjectRootPomParents.sh, with PR applied:

{code}
/home/nboldt/tru/buildci/util/getProjectRootPomParents.sh -updateRootPom -createBranch -b jbosstools-4.4.x -b2 master \
-pv 4.4.1.Final-SNAPSHOT -w1 /tmp/jbosstools.github -p1 "aerogear arquillian base browsersim central discovery forge \
freemarker hibernate javaee jst livereload openshift server vpe webservices" -p2 "build build-sites" -p3 "devdoc product" \
| tee log.txt{code}

[^console.log.txt]

Scriptlet created when you run getProjectRootPomParents.sh, which someone with God Mode Powers on the various repos can then run:

[^getProjectRootPomParents.tsk.txt]

Note that running this eats about 500M of disk (for the github shallow clones), and takes about 3-4 minutes to run. 

I have only partially tested the resulting scriptlet as I can't run most of it (don't have permissions). But it DOES work for committing changes and creating branches. I've created the 4.4.1.x branch in jbdevstudio-devdoc just to verify it works.

So, now, all I need to do is wrap a Jenkins job around this, and have it also produce JIRA(s) associated with the changes, so they can be tracked.

Good news is that the bzira job is able to create JIRAs so we can do this without needing a particular user's credentials plaintext in the job config.


was (Author: nickboldt):
PR to support fixing root poms and creating branches:

https://github.com/jbosstools/jbosstools-build-ci/pull/152/files

Sample run of getProjectRootPomParents.sh, with PR applied:

{code}
/home/nboldt/tru/buildci/util/getProjectRootPomParents.sh -updateRootPom -createBranch -b jbosstools-4.4.x -b2 master \
-pv 4.4.1.Final-SNAPSHOT -w1 /tmp/jbosstools.github -p1 "aerogear arquillian base browsersim central discovery forge \
freemarker hibernate javaee jst livereload openshift server vpe webservices" -p2 "build build-sites" -p3 "devdoc product" \
| tee log.txt{code}

[^console.log.txt]

Scriptlet created when you run getProjectRootPomParents.sh, which someone with God Mode Powers on the various repos can then run:

[^getProjectRootPomParents.tsk.txt]

Note that running this eats about 500M of disk (for the github shallow clones), and takes about 3-4 minutes to run. 

I have only partially tested the resulting scriptlet as I can't run most of it (don't have permissions). But it DOES work for committing changes and creating branches. I've created the 4.4.1.x branch in jbdevstudio-devdoc just to verify it works.

> 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.Final
>
>         Attachments: console.log.txt, getProjectRootPomParents.tsk.txt
>
>
> 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)