[JBoss JIRA] (JBIDE-23092) add more projects to the list of projects to branch and/or update root pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23092?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23092:
------------------------------------
I've added the above list to the job config, so next time around we can branch all the other projects too:
Meanwhile, I've branched the above projects by hand, eg., https://github.com/jbdevstudio/jbdevstudio-website/tree/jbosstools-4.4.1.x
{code}
for d in jbosstools-maven-plugins/ jbosstools-download.jboss.org/ jbosstools-devdoc/ jbosstools-versionwatch/; do pushd $d; git checkout master;git pull origin master;git checkout -b jbosstools-4.4.1.x;git push origin jbosstools-4.4.1.x; popd; done
for d in jbdevstudio-artwork/ jbdevstudio-website/ jbdevstudio-ci/; do pushd $d; git checkout master;git pull origin master;git checkout -b jbosstools-4.4.1.x;git push origin jbosstools-4.4.1.x; popd; done
{code}
I can't branch jbdevstudio-qa since I don't have permission.
> add more projects to the list of projects to branch and/or update root pom
> --------------------------------------------------------------------------
>
> Key: JBIDE-23092
> URL: https://issues.jboss.org/browse/JBIDE-23092
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> MIssing projects we could have included in the automated branching:
> * jbosstools-integration-tests [root pom in ./]
> Need to also branch these, but there's no root pom to adjust, so the script should just fail silently:
> * jbosstools-devdoc [no root pom]
> * jbosstools-download.jboss.org [no root pom]
> * jbosstools-maven-plugins no root pom]
> * jbosstools-versionwatch [no root pom]
> * jbdevstudio-ci [no root pom]
> * jbdevstudio-qa [no root pom]
> * jbdevstudio-website [no root pom]
> * jbdevstudio-artwork [no root pom]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23092) add more projects to the list of projects to branch and/or update root pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23092?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-23092:
----------------------------------
Assignee: Nick Boldt
> add more projects to the list of projects to branch and/or update root pom
> --------------------------------------------------------------------------
>
> Key: JBIDE-23092
> URL: https://issues.jboss.org/browse/JBIDE-23092
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> MIssing projects we could have included in the automated branching:
> * jbosstools-integration-tests [root pom in ./]
> Need to also branch these, but there's no root pom to adjust, so the script should just fail silently:
> * jbosstools-devdoc [no root pom]
> * jbosstools-download.jboss.org [no root pom]
> * jbosstools-maven-plugins no root pom]
> * jbosstools-versionwatch [no root pom]
> * jbdevstudio-ci [no root pom]
> * jbdevstudio-qa [no root pom]
> * jbdevstudio-website [no root pom]
> * jbdevstudio-artwork [no root pom]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23092) add more projects to the list of projects to branch and/or update root pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23092?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-23092.
--------------------------------
Resolution: Done
> add more projects to the list of projects to branch and/or update root pom
> --------------------------------------------------------------------------
>
> Key: JBIDE-23092
> URL: https://issues.jboss.org/browse/JBIDE-23092
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> MIssing projects we could have included in the automated branching:
> * jbosstools-integration-tests [root pom in ./]
> Need to also branch these, but there's no root pom to adjust, so the script should just fail silently:
> * jbosstools-devdoc [no root pom]
> * jbosstools-download.jboss.org [no root pom]
> * jbosstools-maven-plugins no root pom]
> * jbosstools-versionwatch [no root pom]
> * jbdevstudio-ci [no root pom]
> * jbdevstudio-qa [no root pom]
> * jbdevstudio-website [no root pom]
> * jbdevstudio-artwork [no root pom]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23074) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Integration Tests]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23074?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-23074:
----------------------------------
Assignee: Martin Malina
> For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Integration Tests]
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23074
> URL: https://issues.jboss.org/browse/JBIDE-23074
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: qa
> Reporter: Friendly Jira Robot
> Assignee: Martin Malina
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.Final
>
>
> For JBIDE 4.4.1.Final [Integration Tests]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch:
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.1.x
> git push origin jbosstools-4.4.1.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 5. Close (do not resolve) this JIRA when done.
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23092) add more projects to the list of projects to branch and/or update root pom
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23092?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-23092:
----------------------------------------
Ah, there is jbdevstudio-website in the list. Not jbosstools-website. So, let's tag/branch jbdevstudio-website.
> add more projects to the list of projects to branch and/or update root pom
> --------------------------------------------------------------------------
>
> Key: JBIDE-23092
> URL: https://issues.jboss.org/browse/JBIDE-23092
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> MIssing projects we could have included in the automated branching:
> * jbosstools-integration-tests [root pom in ./]
> Need to also branch these, but there's no root pom to adjust, so the script should just fail silently:
> * jbosstools-devdoc [no root pom]
> * jbosstools-download.jboss.org [no root pom]
> * jbosstools-maven-plugins no root pom]
> * jbosstools-versionwatch [no root pom]
> * jbdevstudio-ci [no root pom]
> * jbdevstudio-qa [no root pom]
> * jbdevstudio-website [no root pom]
> * jbdevstudio-artwork [no root pom]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23070) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23070?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-23070.
------------------------------
Resolution: Done
> For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA
> ----------------------------------------------------------
>
> Key: JBIDE-23070
> URL: https://issues.jboss.org/browse/JBIDE-23070
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Friendly Jira Robot
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.Final
>
>
> For JBIDE 4.4.1.Final: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch:
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.1.x
> git push origin jbosstools-4.4.1.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 5. Close (do not resolve) this JIRA when done.
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-4040
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23075) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23075?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-23075.
------------------------------
Resolution: Done
> For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23075
> URL: https://issues.jboss.org/browse/JBIDE-23075
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Friendly Jira Robot
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.Final
>
>
> For JBIDE 4.4.1.Final [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch:
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.1.x
> git push origin jbosstools-4.4.1.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 5. Close (do not resolve) this JIRA when done.
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23070) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23070?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-23070:
----------------------------------
Assignee: Nick Boldt
> For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA
> ----------------------------------------------------------
>
> Key: JBIDE-23070
> URL: https://issues.jboss.org/browse/JBIDE-23070
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Friendly Jira Robot
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.Final
>
>
> For JBIDE 4.4.1.Final: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch:
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.1.x
> git push origin jbosstools-4.4.1.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 5. Close (do not resolve) this JIRA when done.
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-4040
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months