[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:
-------------------------------
Sprint: devex #1 February 2016
> 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
>
> Attachments: config.xml
>
>
> 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 updated JBIDE-21642:
-------------------------------
Story Points: 3
> 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
>
> Attachments: config.xml
>
>
> 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 closed JBIDE-21642.
------------------------------
Resolution: Done
Closing as this works! :D
> 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
>
> Attachments: config.xml
>
>
> 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 updated JBIDE-21642:
-------------------------------
Attachment: config.xml
Configuration for building Birt 1.8.0 from the 1.8.0.Final tag, and forcing BUILD_ID and BUILD_NUMBER to their old values:
[^config.xml]
> 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
>
> Attachments: config.xml
>
>
> 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-21630) itest timeout not respected
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21630?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-21630 at 2/4/16 9:40 AM:
------------------------------------------------------------
setting 4000 still failed.
With
*mvn help:effective-pom verify -Dsurefire.itests.timeout=8000 -Dsurefire.timeout=8000 -f /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/all-tests/pom.xml*
we get:
{code}
[jbosstools-server_master] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -f /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/all-tests/pom.xml -DTARGET_PLATFORM_VERSION=4.60.0.Alpha1-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.60.0.Alpha1-SNAPSHOT "-DMAVEN_FLAGS=-B -U -fae -e -Djbosstools_site_stream=master -P hudson,pack200,unified.target -Dsurefire.itests.timeout=8000 -Dsurefire.timeout=8000" -DskipRevisionCheckWhenPublishing=true -Ddownload.cache.directory=/home/hudson/static_build_env/jbds/download-cache -DJOB_NAME=jbosstools-server_master -DBUILD_NUMBER=913 -DBUILD_ID=2016-02-03_16-09-00 -DskipPrivateRequirements=false -Djbosstools.test.jre.8=/qa/tools/opt/amd64/jdk1.8.0_last -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 -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true -DskipBaselineComparison=true -Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-server_master/.repository help:effective-pom verify -B -U -fae -e -Djbosstools_site_stream=master -P hudson,pack200,unified.target -Dsurefire.itests.timeout=8000 -Dsurefire.timeout=8000 -gs /home/hudson/.m2/settings.xml -DTARGET_PLATFORM_VERSION=4.60.0.Alpha1-SNAPSHOT
...
<surefire.itests.timeout>3000</surefire.itests.timeout>
<surefire.timeout>2400</surefire.timeout>
...
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:07 h
{code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
And we're back to 3434 tests being run and recorded, once again on slave dev112.
!jbide21630.png!
!jbide21630-tests.png!
was (Author: nickboldt):
setting 4000 still failed.
With
*mvn help:effective-pom verify -Dsurefire.itests.timeout=8000 -Dsurefire.timeout=8000 -f /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/all-tests/pom.xml*
we get:
{code}
[jbosstools-server_master] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -f /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/all-tests/pom.xml -DTARGET_PLATFORM_VERSION=4.60.0.Alpha1-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.60.0.Alpha1-SNAPSHOT "-DMAVEN_FLAGS=-B -U -fae -e -Djbosstools_site_stream=master -P hudson,pack200,unified.target -Dsurefire.itests.timeout=8000 -Dsurefire.timeout=8000" -DskipRevisionCheckWhenPublishing=true -Ddownload.cache.directory=/home/hudson/static_build_env/jbds/download-cache -DJOB_NAME=jbosstools-server_master -DBUILD_NUMBER=913 -DBUILD_ID=2016-02-03_16-09-00 -DskipPrivateRequirements=false -Djbosstools.test.jre.8=/qa/tools/opt/amd64/jdk1.8.0_last -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 -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true -DskipBaselineComparison=true -Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-server_master/.repository help:effective-pom verify -B -U -fae -e -Djbosstools_site_stream=master -P hudson,pack200,unified.target -Dsurefire.itests.timeout=8000 -Dsurefire.timeout=8000 -gs /home/hudson/.m2/settings.xml -DTARGET_PLATFORM_VERSION=4.60.0.Alpha1-SNAPSHOT
...
<surefire.itests.timeout>3000</surefire.itests.timeout>
<surefire.timeout>2400</surefire.timeout>
...
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:07 h
{code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> itest timeout not respected
> ---------------------------
>
> Key: JBIDE-21630
> URL: https://issues.jboss.org/browse/JBIDE-21630
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Labels: help_wanted
> Fix For: 4.4.0.Alpha1
>
> Attachments: jbide21630-tests.png, jbide21630.png
>
>
> Server itests are running with a timeout of 2400s, which is the default set in our parent pom [1].
> [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
> But the server root pom sets a timeout of 3000s [2], which is being ignored [3]:
> [2] https://github.com/jbosstools/jbosstools-server/blob/master/pom.xml#L17-L18
> {code}
> 13:39:42 [ERROR] Timeout 2400 s exceeded. Process was killed.
> {code}
> [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> So... how can we ensure that the itests get more time to run, so that these extra tests can be run without crashing? Currently, server is showing 2829 tests, but the last time it was blue, we had 3434 tests, so there are about 600 tests for which no results are being logged due to the timeout.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21630) itest timeout not respected
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21630?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21630:
------------------------------------
setting 4000 still failed.
With
*mvn help:effective-pom verify -Dsurefire.itests.timeout=8000 -Dsurefire.timeout=8000 -f /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/all-tests/pom.xml*
we get:
{code}
[jbosstools-server_master] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -f /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/all-tests/pom.xml -DTARGET_PLATFORM_VERSION=4.60.0.Alpha1-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.60.0.Alpha1-SNAPSHOT "-DMAVEN_FLAGS=-B -U -fae -e -Djbosstools_site_stream=master -P hudson,pack200,unified.target -Dsurefire.itests.timeout=8000 -Dsurefire.timeout=8000" -DskipRevisionCheckWhenPublishing=true -Ddownload.cache.directory=/home/hudson/static_build_env/jbds/download-cache -DJOB_NAME=jbosstools-server_master -DBUILD_NUMBER=913 -DBUILD_ID=2016-02-03_16-09-00 -DskipPrivateRequirements=false -Djbosstools.test.jre.8=/qa/tools/opt/amd64/jdk1.8.0_last -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 -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true -DskipBaselineComparison=true -Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-server_master/.repository help:effective-pom verify -B -U -fae -e -Djbosstools_site_stream=master -P hudson,pack200,unified.target -Dsurefire.itests.timeout=8000 -Dsurefire.timeout=8000 -gs /home/hudson/.m2/settings.xml -DTARGET_PLATFORM_VERSION=4.60.0.Alpha1-SNAPSHOT
...
<surefire.itests.timeout>3000</surefire.itests.timeout>
<surefire.timeout>2400</surefire.timeout>
...
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:07 h
{code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> itest timeout not respected
> ---------------------------
>
> Key: JBIDE-21630
> URL: https://issues.jboss.org/browse/JBIDE-21630
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Labels: help_wanted
> Fix For: 4.4.0.Alpha1
>
>
> Server itests are running with a timeout of 2400s, which is the default set in our parent pom [1].
> [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
> But the server root pom sets a timeout of 3000s [2], which is being ignored [3]:
> [2] https://github.com/jbosstools/jbosstools-server/blob/master/pom.xml#L17-L18
> {code}
> 13:39:42 [ERROR] Timeout 2400 s exceeded. Process was killed.
> {code}
> [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> So... how can we ensure that the itests get more time to run, so that these extra tests can be run without crashing? Currently, server is showing 2829 tests, but the last time it was blue, we had 3434 tests, so there are about 600 tests for which no results are being logged due to the timeout.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months