[
https://issues.jboss.org/browse/JBIDE-22728?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-22728 at 8/26/16 9:04 PM:
-------------------------------------------------------------
Job in progress here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
However, python script seems to by dying if run on a RHEL6 slave with python 2.6. So
I've moved the job to RHEL7, and it works great.
Here's what appears in the generated email:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
was (Author: nickboldt):
Job in progress here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
However, python script seems to by dying ... need to find a slave on which it can run
properly.
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)