February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21642) verify if it's possible to build, deploy, & test a JBT project from an existing tag

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21642?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21642: ------------------------------- Fix Version/s: 4.3.1.CR1 > verify if it's possible to build, deploy, & test a JBT project from an existing tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-21642 > URL: https://issues.jboss.org/browse/JBIDE-21642 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > > Usecase: > We want to rebuild something that we released a few months ago, for which there have been no significant changes (other than bumping feature/plugin versions and using a newer parent pom / target platform). > So, we need a way to run a build from a tag (not a branch) and to ensure that re-deployment to /snapshots/builds/JOBNAME/ works as expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21642) verify if it's possible to build, deploy, & test a JBT project from an existing tag

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21642?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21642: ------------------------------- Affects Version/s: 4.3.1.Beta2 > verify if it's possible to build, deploy, & test a JBT project from an existing tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-21642 > URL: https://issues.jboss.org/browse/JBIDE-21642 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > > Usecase: > We want to rebuild something that we released a few months ago, for which there have been no significant changes (other than bumping feature/plugin versions and using a newer parent pom / target platform). > So, we need a way to run a build from a tag (not a branch) and to ensure that re-deployment to /snapshots/builds/JOBNAME/ works as expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21642) verify if it's possible to build, deploy, & test a JBT project from an existing tag

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21642?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21642: ------------------------------- Component/s: build > verify if it's possible to build, deploy, & test a JBT project from an existing tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-21642 > URL: https://issues.jboss.org/browse/JBIDE-21642 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > > Usecase: > We want to rebuild something that we released a few months ago, for which there have been no significant changes (other than bumping feature/plugin versions and using a newer parent pom / target platform). > So, we need a way to run a build from a tag (not a branch) and to ensure that re-deployment to /snapshots/builds/JOBNAME/ works as expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21643) use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21643?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21643: ------------------------------- Component/s: build > use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ? > --------------------------------------------------------- > > Key: JBIDE-21643 > URL: https://issues.jboss.org/browse/JBIDE-21643 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: birt, build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.3.1.CR1 > > > Since feature freeze is done for Birt 1.8.x in JBT 4.3.1.Beta2, we have two choices for what to include in JBT 4.3.1.CR1 and .Final: > a) since nothing important has happened in the 4.3.x branch [1] of jbosstools-birt, we could re-use the 1.8.0.Final bits, which I've just rebuilt [2] from the 4.3.0.Final tag, and published [3]. > b) or we could upversion the 1.8.1.Beta2 bits to 1.8.1.CR1 (and then later to 1.8.1.Final) even though there's functionally nothing new in there beyond what was released in 1.8.0.Final on Sept 24. > [1] https://github.com/jbosstools/jbosstools-birt/commits/jbosstools-4.3.x > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3.m... > [3] http://download.jboss.org/jbosstools/mars/stable/updates/core/birt/1.8.0.... > I'm inclined to go with the rebuilt 1.8.0 instead of the needlessly upversioned 1.8.1. > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21643) use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21643?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21643: ------------------------------- Description: Since feature freeze is done for Birt 1.8.x in JBT 4.3.1.Beta2, we have two choices for what to include in JBT 4.3.1.CR1 and .Final: a) since nothing important has happened in the 4.3.x branch [1] of jbosstools-birt, we could re-use the 1.8.0.Final bits, which I've just rebuilt [2] from the 4.3.0.Final tag, and published [3]. b) or we could upversion the 1.8.1.Beta2 bits to 1.8.1.CR1 (and then later to 1.8.1.Final) even though there's functionally nothing new in there beyond what was released in 1.8.0.Final on Sept 24. [1] https://github.com/jbosstools/jbosstools-birt/commits/jbosstools-4.3.x [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3.m... [3] http://download.jboss.org/jbosstools/mars/stable/updates/core/birt/1.8.0.... I'm inclined to go with the rebuilt 1.8.0 instead of the needlessly upversioned 1.8.1. WDYT? was: Since feature freeze is done for Birt 1.8.x in JBT 4.3.1.Beta2, we have two choices for what to include in JBT 4.3.1.CR1 and .Final: a) since nothing important has happened in the 4.3.x branch [1] of jbosstools-birt, we could re-use the 1.8.0.Final bits, which I've just rebuilt [2] from the 4.3.0.Final tag, and published [3]. b) or we could upversion the 1.8.1.Beta2 bits to 1.8.1.CR1 (and then later to 1.8.1.Final) even though there's functionally nothing new in there beyond what was released in 1.8.0.Final on Sept 24. [1] https://github.com/jbosstools/jbosstools-birt/commits/jbosstools-4.3.x [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3.m... [3] http://download.jboss.org/jbosstools/updates/stable/mars/core/birt/1.8.0.... I'm inclined to go with the rebuilt 1.8.0 instead of the needlessly upversioned 1.8.1. WDYT? > use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ? > --------------------------------------------------------- > > Key: JBIDE-21643 > URL: https://issues.jboss.org/browse/JBIDE-21643 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: birt > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.3.1.CR1 > > > Since feature freeze is done for Birt 1.8.x in JBT 4.3.1.Beta2, we have two choices for what to include in JBT 4.3.1.CR1 and .Final: > a) since nothing important has happened in the 4.3.x branch [1] of jbosstools-birt, we could re-use the 1.8.0.Final bits, which I've just rebuilt [2] from the 4.3.0.Final tag, and published [3]. > b) or we could upversion the 1.8.1.Beta2 bits to 1.8.1.CR1 (and then later to 1.8.1.Final) even though there's functionally nothing new in there beyond what was released in 1.8.0.Final on Sept 24. > [1] https://github.com/jbosstools/jbosstools-birt/commits/jbosstools-4.3.x > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3.m... > [3] http://download.jboss.org/jbosstools/mars/stable/updates/core/birt/1.8.0.... > I'm inclined to go with the rebuilt 1.8.0 instead of the needlessly upversioned 1.8.1. > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21642) verify if it's possible to build, deploy, & test a JBT project from an existing tag

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21642?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21642: ---------------------------------- Assignee: Nick Boldt > verify if it's possible to build, deploy, & test a JBT project from an existing tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-21642 > URL: https://issues.jboss.org/browse/JBIDE-21642 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Nick Boldt > Assignee: Nick Boldt > > Usecase: > We want to rebuild something that we released a few months ago, for which there have been no significant changes (other than bumping feature/plugin versions and using a newer parent pom / target platform). > So, we need a way to run a build from a tag (not a branch) and to ensure that re-deployment to /snapshots/builds/JOBNAME/ works as expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21643) use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21643?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21643: ---------------------------------- Assignee: Snjezana Peco > use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ? > --------------------------------------------------------- > > Key: JBIDE-21643 > URL: https://issues.jboss.org/browse/JBIDE-21643 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: birt > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.3.1.CR1 > > > Since feature freeze is done for Birt 1.8.x in JBT 4.3.1.Beta2, we have two choices for what to include in JBT 4.3.1.CR1 and .Final: > a) since nothing important has happened in the 4.3.x branch [1] of jbosstools-birt, we could re-use the 1.8.0.Final bits, which I've just rebuilt [2] from the 4.3.0.Final tag, and published [3]. > b) or we could upversion the 1.8.1.Beta2 bits to 1.8.1.CR1 (and then later to 1.8.1.Final) even though there's functionally nothing new in there beyond what was released in 1.8.0.Final on Sept 24. > [1] https://github.com/jbosstools/jbosstools-birt/commits/jbosstools-4.3.x > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3.m... > [3] http://download.jboss.org/jbosstools/updates/stable/mars/core/birt/1.8.0.... > I'm inclined to go with the rebuilt 1.8.0 instead of the needlessly upversioned 1.8.1. > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21643) use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21643?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21643: ------------------------------- Fix Version/s: 4.3.1.CR1 > use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ? > --------------------------------------------------------- > > Key: JBIDE-21643 > URL: https://issues.jboss.org/browse/JBIDE-21643 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: birt > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.3.1.CR1 > > > Since feature freeze is done for Birt 1.8.x in JBT 4.3.1.Beta2, we have two choices for what to include in JBT 4.3.1.CR1 and .Final: > a) since nothing important has happened in the 4.3.x branch [1] of jbosstools-birt, we could re-use the 1.8.0.Final bits, which I've just rebuilt [2] from the 4.3.0.Final tag, and published [3]. > b) or we could upversion the 1.8.1.Beta2 bits to 1.8.1.CR1 (and then later to 1.8.1.Final) even though there's functionally nothing new in there beyond what was released in 1.8.0.Final on Sept 24. > [1] https://github.com/jbosstools/jbosstools-birt/commits/jbosstools-4.3.x > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3.m... > [3] http://download.jboss.org/jbosstools/updates/stable/mars/core/birt/1.8.0.... > I'm inclined to go with the rebuilt 1.8.0 instead of the needlessly upversioned 1.8.1. > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21643) use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21643: ---------------------------------- Summary: use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ? Key: JBIDE-21643 URL: https://issues.jboss.org/browse/JBIDE-21643 Project: Tools (JBoss Tools) Issue Type: Bug Components: birt Affects Versions: 4.3.1.Beta2 Reporter: Nick Boldt Since feature freeze is done for Birt 1.8.x in JBT 4.3.1.Beta2, we have two choices for what to include in JBT 4.3.1.CR1 and .Final: a) since nothing important has happened in the 4.3.x branch [1] of jbosstools-birt, we could re-use the 1.8.0.Final bits, which I've just rebuilt [2] from the 4.3.0.Final tag, and published [3]. b) or we could upversion the 1.8.1.Beta2 bits to 1.8.1.CR1 (and then later to 1.8.1.Final) even though there's functionally nothing new in there beyond what was released in 1.8.0.Final on Sept 24. [1] https://github.com/jbosstools/jbosstools-birt/commits/jbosstools-4.3.x [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3.m... [3] http://download.jboss.org/jbosstools/updates/stable/mars/core/birt/1.8.0.... I'm inclined to go with the rebuilt 1.8.0 instead of the needlessly upversioned 1.8.1. WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21642) verify if it's possible to build, deploy, & test a JBT project from an existing tag

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21642?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-21642 at 2/3/16 9:29 PM: ------------------------------------------------------------ Experimenting with https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3.... to build from *refs/tags/jbosstools-4.3.0.Final* To build using the same details as an old build, we need to pass in multiple overrides for the timestamp and build number: {code}-DBUILD_NUMBER=33 -DBUILD_ID=2015-09-24_22-32-00 -Dmaven.build.timestamp=2015-09-25T04:32:00Z -DforceContextQualifier=Final-v20150924-2232-B33{code} Side note: don't wrap quotes around -DforceContextQualifier="Final-v20150924-2232-B33" when passing it to the bash script that does the deployment, or you get an error: {code} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.23.1:build-qualifier-aggregator (default-build-qualifier-aggregator) on project birt.site: Invalid build qualifier, it does not match the OSGi qualifier constraint ([0..9]|[a..zA..Z]|'_'|'-') {code} was (Author: nickboldt): Experimenting with https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3.... to build from *refs/tags/jbosstools-4.3.0.Final* First thing we need to do is pass in multiple overrides for the timestamp and build number: {code}-DBUILD_NUMBER=33 -DBUILD_ID=2015-09-24_22-32-00 -Dmaven.build.timestamp=2015-09-25T04:32:00Z -DforceContextQualifier=Final-v20150924-2232-B33{code} Seems the first problem is that we can't do a clean install followed by a deploy because: {code} + /qa/tools/opt/apache-maven-3.2.5//bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-birt_4.3.mars/.repository -Djbosstools_site_stream= -B -U -fae -e -Djbosstools_site_stream=4.3.mars -P hudson,pack200,unified.target -DBUILD_NUMBER=33 -DBUILD_ID=2015-09-24_22-32-00 -Dmaven.build.timestamp=2015-09-25T04:32:00Z '-DforceContextQualifier="Final-v20150924-2232-B33"' ... [WARNING] The following locally built units have been used to resolve project dependencies: [WARNING] org.jboss.tools.birt.feature.feature.group/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.test.feature.source.feature.group/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.core/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.oda.ui/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.feature.source.feature.group/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.test.feature.feature.group/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.test.feature.feature.jar/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.feature.source.feature.jar/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.test.feature.source.feature.jar/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.oda.ui.source/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.oda.source/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.core.source/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.oda/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.core.test/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.core.test.source/1.8.0.Final-v20150924-2232-B33 [WARNING] org.jboss.tools.birt.feature.feature.jar/1.8.0.Final-v20150924-2232-B33 ... [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.23.1:build-qualifier-aggregator (default-build-qualifier-aggregator) on project birt.site: Invalid build qualifier, it does not match the OSGi qualifier constraint ([0..9]|[a..zA..Z]|'_'|'-') -> [Help 1]{code} So we can do build & deployment in one step: {code} [jbosstools-birt_4.3.mars.0] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -f /mnt/hudson_workspace/workspace/jbosstools-birt_4.3.mars.0/sources/pom.xml -DTARGET_PLATFORM_VERSION=4.50.2.Beta2-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.52.0.Beta2-SNAPSHOT '-DMAVEN_FLAGS=-B -U -fae -e -Djbosstools_site_stream=4.3.mars -P hudson,pack200,unified.target -DBUILD_NUMBER=33 -DBUILD_ID=2015-09-24_22-32-00 -Dmaven.build.timestamp=2015-09-25T04:32:00Z -DforceContextQualifier="Final-v20150924-2232-B33"' -DskipRevisionCheckWhenPublishing=true -Ddownload.cache.directory=/home/hudson/static_build_env/jbds/download-cache -Dmaven.test.skip=true -DJOB_NAME=jbosstools-birt_4.3.mars.0 -DBUILD_NUMBER=1 -DBUILD_ID=2016-02-03_19-16-22 -DskipPrivateRequirements=false -Djbosstools.test.jre.8=/qa/tools/opt/amd64/jdk1.8.0_last -DskipITests=true -Djbosstools.test.jre.7=/qa/tools/opt/amd64/jdk1.7.0_last -Djbosstools.test.jre.6=/qa/tools/opt/amd64/jdk1.6.0_last -Djbosstools.test.jre.5=/qa/tools/opt/amd64/jdk1.5.0_last -DskipBaselineComparison=false -Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-birt_4.3.mars.0/.repository clean deploy -Pdeploy-to-jboss.org -B -U -fae -e -Djbosstools_site_stream=4.3.mars -P hudson,pack200,unified.target -DBUILD_NUMBER=33 -DBUILD_ID=2015-09-24_22-32-00 -Dmaven.build.timestamp=2015-09-25T04:32:00Z -DforceContextQualifier=Final-v20150924-2232-B33 -gs /home/hudson/.m2/settings.xml -DTARGET_PLATFORM_VERSION=4.50.2.Beta2-SNAPSHOT {code} or do the usual build, deploy, then test. Just need to ensure we don't wrap quotes around -DforceContextQualifier="Final-v20150924-2232-B33" when passing it to the bash script that does the deployment. > verify if it's possible to build, deploy, & test a JBT project from an existing tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-21642 > URL: https://issues.jboss.org/browse/JBIDE-21642 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Nick Boldt > > Usecase: > We want to rebuild something that we released a few months ago, for which there have been no significant changes (other than bumping feature/plugin versions and using a newer parent pom / target platform). > So, we need a way to run a build from a tag (not a branch) and to ensure that re-deployment to /snapshots/builds/JOBNAME/ works as expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2016