[JBoss JIRA] (JBIDE-22554) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central Discovery]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22554?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22554:
------------------------------------
Now seeing 10.0.1.AM2-v20160720-1716-B6135.jar and 4.4.1.AM2-v20160720-1715-B6135.jar
> For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central Discovery]
> --------------------------------------------------------------------
>
> Key: JBIDE-22554
> URL: https://issues.jboss.org/browse/JBIDE-22554
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central-update
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.AM2
>
>
> For JBIDE 4.4.1.Alpha1 [Central Discovery]: 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 Central Discovery 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, 8 months
[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22673:
------------------------------------
OK, so ... wouldn't it make sense to do everything with Tycho 0.26-SNAPSHOT? Can we move jbosstools-maven-plugins up to support Tycho 0.26?
> Need better duplicate IU detection when validating target platforms
> -------------------------------------------------------------------
>
> Key: JBIDE-22673
> URL: https://issues.jboss.org/browse/JBIDE-22673
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, target-platform, upstream
> Affects Versions: 4.4.0.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.4.x
>
> Attachments: verify-log.txt
>
>
> As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not.
> {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...?
> Or add a whitelist?{quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22757) jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22757 at 7/22/16 11:06 AM:
--------------------------------------------------------------
Done:
* in jobs, find and replace: BUILD_ID=$\{BUILD_ID}, -DBUILD_ID=$\{BUILD_ID} and $\{BUILD_ID}-B$\{BUILD_NUMBER} (including Reddeer jobs, cc: [~mmalina] )
* jbosstools-build-ci/publish/rsync.sh
* jbosstools-build-ci/publish/publish.sh (deprecated in favour of rsync.sh)
* jbosstools-build-ci/util/cleanup/jbosstools-cleanup.sh
* jbosstools-build-ci/publish/build-jbosstools-component.sh
* jbosstools-build-ci/buildchow/templates/*.yaml
* jbosstools-locus/site/pom.xml
* jbosstools-versionwatch/run.jenkins.job.sh
Updated list of things to still fix:
* jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo.java
* jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/CreateFullSiteMojo.java
And things for which PRs are needed:
* reddeer/site/pom.xml
* jbosstools-integration-stack/scripts/build.xml
* jbosstools-integration-stack/jbosstools/README.adoc
* jbosstools-integration-stack/\*/\*/\*/pom.xml
* jbosstools-browsersim/products/browsersim-standalone/pom.xml
was (Author: nickboldt):
Done:
* in jobs, find and replace: BUILD_ID=$\{BUILD_ID}, -DBUILD_ID=$\{BUILD_ID} and $\{BUILD_ID}-B$\{BUILD_NUMBER} (including Reddeer jobs, cc: [~mmalina] )
* jbosstools-build-ci/publish/rsync.sh
* jbosstools-build-ci/publish/publish.sh (deprecated in favour of rsync.sh)
* jbosstools-build-ci/util/cleanup/jbosstools-cleanup.sh
* jbosstools-build-ci/publish/build-jbosstools-component.sh
* jbosstools-build-ci/buildchow/templates/*.yaml
* jbosstools-locus/site/pom.xml
* jbosstools-versionwatch/run.jenkins.job.sh
Updated list of things to still fix:
* jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo.java
* jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/CreateFullSiteMojo.java
And things for which PRs are needed:
* reddeer/site/pom.xml
* jbosstools-integration-stack/scripts/build.xml
* jbosstools-integration-stack/jbosstools/README.adoc
* jbosstools-integration-stack/*/*/*/pom.xml
* jbosstools-browsersim/products/browsersim-standalone/pom.xml
> jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
> -----------------------------------------------------------------
>
> Key: JBIDE-22757
> URL: https://issues.jboss.org/browse/JBIDE-22757
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.1.AM2
>
> Attachments: buildID-broken.png
>
>
> Due to an upstream bug in Jenkins [1], [2], BUILD_ID now = BUILD_NUMBER.
> [1] https://issues.jenkins-ci.org/browse/JENKINS-26520
> [2] https://issues.jenkins-ci.org/browse/JENKINS-26626
> So instead of timestamped build folders, we're seeing things like this:
> !buildID-broken.png|thumbnail!
> Workaround until fixed in Jenkins:
> {code}BUILD_ID=`date -u +%Y-%m-%d_%H-%M-%S`{code}
> Or, try using BUILD_TIMESTAMP instead?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22757) jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22757:
------------------------------------
Done:
* in jobs, find and replace: BUILD_ID=$\{BUILD_ID}, -DBUILD_ID=$\{BUILD_ID} and $\{BUILD_ID}-B$\{BUILD_NUMBER} (including Reddeer jobs, cc: [~mmalina] )
* jbosstools-build-ci/publish/rsync.sh
* jbosstools-build-ci/publish/publish.sh (deprecated in favour of rsync.sh)
* jbosstools-build-ci/util/cleanup/jbosstools-cleanup.sh
* jbosstools-build-ci/publish/build-jbosstools-component.sh
* jbosstools-build-ci/buildchow/templates/*.yaml
* jbosstools-locus/site/pom.xml
* jbosstools-versionwatch/run.jenkins.job.sh
Updated list of things to still fix:
* jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo.java
* jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/CreateFullSiteMojo.java
And things for which PRs are needed:
* reddeer/site/pom.xml
* jbosstools-integration-stack/scripts/build.xml
* jbosstools-integration-stack/jbosstools/README.adoc
* jbosstools-integration-stack/*/*/*/pom.xml
* jbosstools-browsersim/products/browsersim-standalone/pom.xml
> jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
> -----------------------------------------------------------------
>
> Key: JBIDE-22757
> URL: https://issues.jboss.org/browse/JBIDE-22757
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.1.AM2
>
> Attachments: buildID-broken.png
>
>
> Due to an upstream bug in Jenkins [1], [2], BUILD_ID now = BUILD_NUMBER.
> [1] https://issues.jenkins-ci.org/browse/JENKINS-26520
> [2] https://issues.jenkins-ci.org/browse/JENKINS-26626
> So instead of timestamped build folders, we're seeing things like this:
> !buildID-broken.png|thumbnail!
> Workaround until fixed in Jenkins:
> {code}BUILD_ID=`date -u +%Y-%m-%d_%H-%M-%S`{code}
> Or, try using BUILD_TIMESTAMP instead?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months