[JBoss JIRA] (JBIDE-22557) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22557?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22557:
------------------------------------
* build: change to BUILD_ALIAS=AM2 and use maven-plugins 0.25.1-SNAPSHOT instead of 0.25.0-SNAPSHOT
> For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22557
> URL: https://issues.jboss.org/browse/JBIDE-22557
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.AM1, 4.4.1.AM2
>
>
> For JBIDE 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks:
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [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, 9 months
[JBoss JIRA] (JBIDE-22680) Create CI jobs running integration tests on incoming PRs
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22680?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-22680:
----------------------------------------
It might be caused by both job using the same "Commit Status Context" in the trigger configuration (value is "Red Hat Jenkins" for both). Can you try again with a different value of Commit Status Context for both jobs?
> Create CI jobs running integration tests on incoming PRs
> --------------------------------------------------------
>
> Key: JBIDE-22680
> URL: https://issues.jboss.org/browse/JBIDE-22680
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, qa
> Reporter: Mickael Istria
> Assignee: Rastislav Wagner
> Fix For: 4.4.x
>
>
> Once we have integration tests running against a given source (JBIDE-22679), let's create the CI jobs to run those automatically and vote on incoming pull requests.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months