[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-12974 at 12/23/12 4:31 PM:
--------------------------------------------------------------
Building running here [0] from my fork [1] (uses this PR [2]).
[0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati...
[1] https://github.com/nickboldt/jbosstools-integration-tests/tree/JBIDE-12974_2
[2] https://github.com/jbosstools/jbosstools-integration-tests/pull/94
To run locally, you need these settings:
{code}
mvn clean install -P jbosstools-nightly-staging-composite-soa-tooling,multiple.target -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true
{code}
Still having some problems w/ test failures in a couple test plugins, which is why I've running with -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true
{code}
./org.jboss.ide.eclipse.as.ui.bot.test/target/surefire-reports/org.jboss.ide.eclipse.as.ui.bot.test.AllTestsSuite.txt
Tests run: 48, Failures: 0, Errors: 48, Skipped: 0, Time elapsed: 493.442 sec <<< FAILURE!
./org.jboss.tools.drools.ui.bot.test/target/surefire-reports/org.jboss.tools.drools.ui.bot.test.DroolsAllBotTests.txt
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.24 sec <<< FAILURE!
./org.jboss.tools.runtime.as.ui.bot.test/target/surefire-reports/org.jboss.tools.runtime.as.ui.bot.test.ProjectTestsSuite.txt
Tests run: 12, Failures: 0, Errors: 12, Skipped: 0, Time elapsed: 39.82 sec <<< FAILURE!
{code}
was (Author: nickboldt):
Building running here [0] from my fork [1] (uses this PR [2]).
[0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati...
[1] https://github.com/nickboldt/jbosstools-integration-tests/tree/JBIDE-12974_2
[2] https://github.com/jbosstools/jbosstools-integration-tests/pull/94
To run locally, you need these settings:
{code}
mvn clean install -P jbosstools-nightly-staging-composite-soa-tooling,multiple.target -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true
{code}
Still having some problems w/ test failures in a couple test plugins, which is why I've running with -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true
{code}
./org.jboss.ide.eclipse.as.ui.bot.test/target/surefire-reports/org.jboss.ide.eclipse.as.ui.bot.test.AllTestsSuite.txt
./org.jboss.tools.drools.ui.bot.test/target/surefire-reports/org.jboss.tools.drools.ui.bot.test.DroolsAllBotTests.txt
./org.jboss.tools.runtime.as.ui.bot.test/target/surefire-reports/org.jboss.tools.runtime.as.ui.bot.test.ProjectTestsSuite.txt
{code}
> add missing IUs to coretests and soatests sites
> -----------------------------------------------
>
> Key: JBIDE-12974
> URL: https://issues.jboss.org/browse/JBIDE-12974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing, updatesite
> Affects Versions: 4.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.x
>
>
> The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content.
> [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/
> [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/
> Are there any other missing IUs you need on those sites?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-12974 at 12/23/12 4:31 PM:
--------------------------------------------------------------
Building running here [0] from my fork [1] (uses this PR [2]).
[0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati...
[1] https://github.com/nickboldt/jbosstools-integration-tests/tree/JBIDE-12974_2
[2] https://github.com/jbosstools/jbosstools-integration-tests/pull/94
To run locally, you need these settings:
{code}
mvn clean install -P jbosstools-nightly-staging-composite-soa-tooling,multiple.target -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true
{code}
Still having some problems w/ test failures in a couple test plugins, which is why I'm running with -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true
{code}
./org.jboss.ide.eclipse.as.ui.bot.test/target/surefire-reports/org.jboss.ide.eclipse.as.ui.bot.test.AllTestsSuite.txt
Tests run: 48, Failures: 0, Errors: 48, Skipped: 0, Time elapsed: 493.442 sec <<< FAILURE!
./org.jboss.tools.drools.ui.bot.test/target/surefire-reports/org.jboss.tools.drools.ui.bot.test.DroolsAllBotTests.txt
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.24 sec <<< FAILURE!
./org.jboss.tools.runtime.as.ui.bot.test/target/surefire-reports/org.jboss.tools.runtime.as.ui.bot.test.ProjectTestsSuite.txt
Tests run: 12, Failures: 0, Errors: 12, Skipped: 0, Time elapsed: 39.82 sec <<< FAILURE!
{code}
was (Author: nickboldt):
Building running here [0] from my fork [1] (uses this PR [2]).
[0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati...
[1] https://github.com/nickboldt/jbosstools-integration-tests/tree/JBIDE-12974_2
[2] https://github.com/jbosstools/jbosstools-integration-tests/pull/94
To run locally, you need these settings:
{code}
mvn clean install -P jbosstools-nightly-staging-composite-soa-tooling,multiple.target -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true
{code}
Still having some problems w/ test failures in a couple test plugins, which is why I've running with -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true
{code}
./org.jboss.ide.eclipse.as.ui.bot.test/target/surefire-reports/org.jboss.ide.eclipse.as.ui.bot.test.AllTestsSuite.txt
Tests run: 48, Failures: 0, Errors: 48, Skipped: 0, Time elapsed: 493.442 sec <<< FAILURE!
./org.jboss.tools.drools.ui.bot.test/target/surefire-reports/org.jboss.tools.drools.ui.bot.test.DroolsAllBotTests.txt
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.24 sec <<< FAILURE!
./org.jboss.tools.runtime.as.ui.bot.test/target/surefire-reports/org.jboss.tools.runtime.as.ui.bot.test.ProjectTestsSuite.txt
Tests run: 12, Failures: 0, Errors: 12, Skipped: 0, Time elapsed: 39.82 sec <<< FAILURE!
{code}
> add missing IUs to coretests and soatests sites
> -----------------------------------------------
>
> Key: JBIDE-12974
> URL: https://issues.jboss.org/browse/JBIDE-12974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing, updatesite
> Affects Versions: 4.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.x
>
>
> The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content.
> [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/
> [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/
> Are there any other missing IUs you need on those sites?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-12973) publish reddeer update site to download.jboss.org
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12973?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-12973:
------------------------------------
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... is running but is having permgen issues. Maybe it needs more memory?
Assuming that it completes and most of the tests are OK, you should get:
* test output
* jacoco coverage report
* archived artifacts
* published results here: http://download.jboss.org/jbosstools/builds/staging/RedDeer_master
Then, when you decide you want to copy a nightly build as an integration build, dev milestone, or stable release, you can run https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/ to perform the copy.
> publish reddeer update site to download.jboss.org
> -------------------------------------------------
>
> Key: JBIDE-12973
> URL: https://issues.jboss.org/browse/JBIDE-12973
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, testing, updatesite
> Affects Versions: 4.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.x
>
>
> Red deer should publish nightly/development/stable update sites like other components of JBT onto download.jboss.org.
> Simplest way to get a nightly build into download.jboss.org/jbosstools/builds/staging/ is to use my publish.sh [1] script as a step during your build job.
> Then, if you want to copy that to a more stable URL (for a dev milestone or stable release) use this job [2]:
> [1] https://svn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-13308) Remove cascading
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13308?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13308:
------------------------------------
Only planning to make changes in trunk for now.
As part of this JIRA, we should also consider renaming jobs to be more "Max-friendly" and replace 4.0/6.0 with 4.1/7.0 in the names.
[~maxandersen] if you have a suggestion for what to call the various component jobs, please feel free to place that here.
{code}
jbosstools-<componentName>_<version>_trunk ?
jbosstools-server_1.4.100_trunk ?
jbosstools-central_4.1_trunk ?
{code}
> Remove cascading
> ----------------
>
> Key: JBIDE-13308
> URL: https://issues.jboss.org/browse/JBIDE-13308
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha1
>
>
> Unlink job by disabling cascading/blocked by upstream. That will make us able to het faster feedback and consume/depend on less Jenkins resources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months