[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:26 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*
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.
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}
> 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
[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:25 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*
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}
was (Author: nickboldt):
Experimenting with https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3....
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 trying to 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}
> 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
[JBoss JIRA] (JBIDE-21069) Application wizard: long project display names mess up project selection
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21069?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21069:
-----------------------------------------------
[~adietish], please take a look at the pull request. The solution limits label length returned by OpenShiftExplorerLabelProvider. That may be of use not only in this case, but in many other viewers that use this label provider.
> Application wizard: long project display names mess up project selection
> ------------------------------------------------------------------------
>
> Key: JBIDE-21069
> URL: https://issues.jboss.org/browse/JBIDE-21069
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jan Richter
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> I've created a project with the longest display name OpenShift would let me. Then when I go to the application wizard and try to select a project from the combo, all hell breaks loose.
> I'm on Gnome with GTK3 and clicking the combo at this point messes up the entire screen to a point that I can't even take a screenshot (sorry I can't show you, it looks awesome). Looks like something overflowing somewhere.
> I also tried a bit shorter name, which just resulted in a selection spanning both my screens and beyond.
> I think cutting the text at certain length and just adding '...' or somthing like that might make it look better.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TOOLSDOC-709) JBDS 9.1 GA: Document a use case for Forge Tooling
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-709?page=com.atlassian.jira.plug... ]
Misha Ali reassigned TOOLSDOC-709:
----------------------------------
Assignee: Misha Ali (was: Supriya Bharadwaj)
> JBDS 9.1 GA: Document a use case for Forge Tooling
> --------------------------------------------------
>
> Key: TOOLSDOC-709
> URL: https://issues.jboss.org/browse/TOOLSDOC-709
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Components: General documentation issues
> Affects Versions: 9.1 GA
> Reporter: Misha Ali
> Assignee: Misha Ali
> Labels: Forge
> Fix For: 9.1 GA
>
>
> Document a use case for Forge tooling.
> 1. Draft a potential use case for what users may want to do with forge.
> 2. Get review on use case idea from a relevant SME or QE person
> 3. Write an intro and flesh out the use case with relevant screenshots
> 4. Get QE review
> 5. Create upstream and downstream versions of approved content.
> a. Add CSP version to customer portal
> b. Send Misha upstream version
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TOOLSDOC-709) JBDS 9.1 GA: Document a use case for Forge Tooling
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-709?page=com.atlassian.jira.plug... ]
Misha Ali reassigned TOOLSDOC-709:
----------------------------------
Assignee: Supriya Bharadwaj (was: Misha Ali)
> JBDS 9.1 GA: Document a use case for Forge Tooling
> --------------------------------------------------
>
> Key: TOOLSDOC-709
> URL: https://issues.jboss.org/browse/TOOLSDOC-709
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Components: General documentation issues
> Affects Versions: 9.1 GA
> Reporter: Misha Ali
> Assignee: Supriya Bharadwaj
> Labels: Forge
> Fix For: 9.1 GA
>
>
> Document a use case for Forge tooling.
> 1. Draft a potential use case for what users may want to do with forge.
> 2. Get review on use case idea from a relevant SME or QE person
> 3. Write an intro and flesh out the use case with relevant screenshots
> 4. Get QE review
> 5. Create upstream and downstream versions of approved content.
> a. Add CSP version to customer portal
> b. Send Misha upstream version
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TOOLSDOC-710) JBDS 9.1 GA: Document a use case for Hibernate Tooling
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-710?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-710:
-------------------------------
Issue Type: Feature Request (was: Bug)
Component/s: General documentation issues
Description: Draft a use case and document it for Hibernate Tools.
Fix Version/s: 9.1 GA
Labels: Hibernate-tools (was: )
Affects Version/s: 9.1 GA
> JBDS 9.1 GA: Document a use case for Hibernate Tooling
> ------------------------------------------------------
>
> Key: TOOLSDOC-710
> URL: https://issues.jboss.org/browse/TOOLSDOC-710
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: General documentation issues
> Affects Versions: 9.1 GA
> Reporter: Misha Ali
> Assignee: Misha Ali
> Labels: Hibernate-tools
> Fix For: 9.1 GA
>
>
> Draft a use case and document it for Hibernate Tools.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TOOLSDOC-709) JBDS 9.1 GA: Document a use case for Forge Tooling
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-709?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-709:
-------------------------------
Sprint: 01-Feb >> 14-Feb 2016-JBDS/JBT (was: 15-Feb >> 28-Feb 2016-JBDS/JBT)
> JBDS 9.1 GA: Document a use case for Forge Tooling
> --------------------------------------------------
>
> Key: TOOLSDOC-709
> URL: https://issues.jboss.org/browse/TOOLSDOC-709
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Components: General documentation issues
> Affects Versions: 9.1 GA
> Reporter: Misha Ali
> Assignee: Supriya Bharadwaj
> Labels: Forge
> Fix For: 9.1 GA
>
>
> Document a use case for Forge tooling.
> 1. Draft a potential use case for what users may want to do with forge.
> 2. Get review on use case idea from a relevant SME or QE person
> 3. Write an intro and flesh out the use case with relevant screenshots
> 4. Get QE review
> 5. Create upstream and downstream versions of approved content.
> a. Add CSP version to customer portal
> b. Send Misha upstream version
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TOOLSDOC-705) JBDS 9.1 Beta2: Release Notes
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-705?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-705:
------------------------------------
Yep, I've changed the order already, so we should be OK now. [~mlabuda], [~mmalina], can you have a look and confirm this is OK to release or if you have any further feedback please?
> JBDS 9.1 Beta2: Release Notes
> -----------------------------
>
> Key: TOOLSDOC-705
> URL: https://issues.jboss.org/browse/TOOLSDOC-705
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: Release Notes
> Affects Versions: 9.1 Beta2
> Reporter: Misha Ali
> Assignee: Misha Ali
> Fix For: 9.1 Beta2
>
>
> Create new Beta2 release notes, fix the script and update the relevant details.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[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 commented on JBIDE-21642:
------------------------------------
Experimenting with https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3....
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 trying to 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}
> 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