[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)
issues at jboss.org
Thu Aug 11 09:35:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-22728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277902#comment-13277902 ]
Max Rydahl Andersen commented on JBIDE-22728:
---------------------------------------------
I took a quick look and couldn't even see any jbdevstudio repos listed. Do you have an example of where a PR is automatically linked into jira ?
If not, jbdevstudio is not even configured for basic linking.
open issue with helpdesk.
> 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)
More information about the jbosstools-issues
mailing list