[JBoss JIRA] (JBIDE-24020) set better defaults for jbosstools.test.jre.* in parent pom?
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-24020:
----------------------------------
Summary: set better defaults for jbosstools.test.jre.* in parent pom?
Key: JBIDE-24020
URL: https://issues.jboss.org/browse/JBIDE-24020
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.5.0.AM1
Reporter: Nick Boldt
A few builds, such as jbosstools-server and jbosstools-webservices, rely on some ancient JREs which are not actually available on the machines on which builds or tests are run.
These JREs are defined in the parent pom here:
https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
Then in Jenkins, the actual paths are defined.
But to run locally & not have tests fail, you therefore need set these via commandline or in your settings.xml file.
So, why not set a better default that works on Windows/Linux/MacOS? How about this?
{code}
-Djbosstools.test.jre.5=${JAVA_HOME}
-Djbosstools.test.jre.6=${JAVA_HOME}
-Djbosstools.test.jre.7=${JAVA_HOME}
-Djbosstools.test.jre.8=${JAVA_HOME}{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24019) test failures in webservices
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24019?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24019:
-------------------------------
Description:
See https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
When I run the same build locally (`mvn clean install`), I get null pointers - and they're not all related to ancient JRE5 tests. See attached: [^org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt]
Running again now with `mvn clean install -Djbosstools.test.jre.5=${JAVA_HOME} -Djbosstools.test.jre.6=${JAVA_HOME} -Djbosstools.test.jre.7=${JAVA_HOME} -Djbosstools.test.jre.8=${JAVA_HOME}` now.
(Wondering if we ought to update the parent pom to have smart defaults for these jbosstools.test.jre.* variables. WDYT?)
was:
See https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
When I run the same build locally, I get null pointers - and they're not all related to ancient JRE5 tests. See attached: [^org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt]
> test failures in webservices
> ----------------------------
>
> Key: JBIDE-24019
> URL: https://issues.jboss.org/browse/JBIDE-24019
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 4.5.0.AM1
>
> Attachments: org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt
>
>
> See https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
> When I run the same build locally (`mvn clean install`), I get null pointers - and they're not all related to ancient JRE5 tests. See attached: [^org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt]
> Running again now with `mvn clean install -Djbosstools.test.jre.5=${JAVA_HOME} -Djbosstools.test.jre.6=${JAVA_HOME} -Djbosstools.test.jre.7=${JAVA_HOME} -Djbosstools.test.jre.8=${JAVA_HOME}` now.
> (Wondering if we ought to update the parent pom to have smart defaults for these jbosstools.test.jre.* variables. WDYT?)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23019) Integration tests: have them running automatically, continuously
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23019?page=com.atlassian.jira.plugi... ]
Jan Richter updated JBIDE-23019:
--------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.3.Final)
> Integration tests: have them running automatically, continuously
> ----------------------------------------------------------------
>
> Key: JBIDE-23019
> URL: https://issues.jboss.org/browse/JBIDE-23019
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: integration-tests, openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Radim Hopp
> Labels: integration_tests
> Fix For: 4.5.0.AM1
>
>
> The integration tests suite is very lenghty to run and should thus be run in a continuous manner on our CI.
> There are several pain-points currently:
> - there's no dedicated OS instance to run them against
> - tests are not stable
> - etc.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months