[
https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin....
]
Rastislav Wagner edited comment on JBDS-4077 at 10/18/16 4:08 AM:
------------------------------------------------------------------
[~nickboldt]
I've setup 3 jobs to run deltaspike integration tests against preinstalled devstudio
1. master deltaspike tests with devstudio 10.1.0.GA
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop...
2. master deltaspike tests with devstudio 10.2.0.AM1
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop...
3. master deltaspike tests with devstudio 10.2.0.AM2
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop...
So the only thing that is different between these jobs is version of devstudio. First two
pass (1 failure is expected), third one fails completely.
We can also take a look at how devstudio looks like in these 3 jobs:
1. job
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop...
2. job
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop...
3. job
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop...
So 1. and 2. looks normal - just like devstudio, 3. looks like eclipse (see title - Java
EE, not Devstudio, also no central tool item etc.)
Eclipse log from 3. job -
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop...
- especially {code}
!ENTRY org.eclipse.equinox.app 0 0 2016-10-18 03:32:07.216
!MESSAGE Product com.jboss.devstudio.core.product could not be found
{code}
It does not look like problem is in our tests/pom.xml :/
was (Author: rawagner):
[~nickboldt]
I've setup 3 jobs to run deltaspike integration tests against preinstalled devstudio
1. master deltaspike tests with devstudio 10.1.0.GA
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop...
2. master deltaspike tests with devstudio 10.2.0.AM1
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop...
3. master deltaspike tests with devstudio 10.2.0.AM2
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop...
So the only thing that is different between these jobs is version of devstudio. First two
pass (1 failure is expected), third one fails completely.
We can also take a look at how devstudio looks like in these 3 jobs:
1. job
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop...
2. job
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop...
3. job
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop...
So 1. and 2. looks normal - just like devstudio, 3. looks like eclipse (see title - Java
EE, not Devstudio, also no central tool item etc.)
It does not look like problem is in our tests/pom.xml :/
Cannot run integration tests against Devstudio with latest target
platform
--------------------------------------------------------------------------
Key: JBDS-4077
URL:
https://issues.jboss.org/browse/JBDS-4077
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: build, target-platform
Affects Versions: 10.2.0.AM1
Reporter: Jan Richter
Assignee: Marián Labuda
Priority: Blocker
Fix For: 10.2.0.AM3
Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg,
no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt,
org.jboss.tools.deltaspike.ui.bot.test.log.txt,
org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png,
Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png,
Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png,
Screenshot_2016-10-05_10-01-32.png, shell.png,
TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png
Integration tests run from maven against Devstudio, which was built using the latest
target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail
afterwards.
A full devstudio should open when the tests are run. Instead it looks like this:
!tpfail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)