[JBoss JIRA] (JBIDE-24656) Split CDK3 server adapter integration tests into separated classes
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24656?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24656:
----------------------------------
Sprint: devex #137 September 2017 (was: devex #136 August 2017)
> Split CDK3 server adapter integration tests into separated classes
> ------------------------------------------------------------------
>
> Key: JBIDE-24656
> URL: https://issues.jboss.org/browse/JBIDE-24656
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.5.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.5.x
>
>
> I decided to divide quite time-consuming CDK server adapter integration tests into smaller test cases due to time that is needed to run all of these test cases in one test class. The one class with all server adapter test cases will be divide into 4 independent classes.
> org.jboss.tools.cdk.ui.bot.test.server.adapter.CDK3IntegrationTest will be split into
> CDK3IntegrationStartTest
> CDK3IntegrationRestartTest
> CDK3IntegrationDockerTest
> CDK3IntegrationOpenshiftTest
> It will be possible to run cdk pr-check job much faster, if it would contain only one complex test case, instead of 4 test cases that each requires to start cdk 3 server adapter.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24883) Python on windows slaves
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24883?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-24883:
-------------------------------
Sprint: devex #137 September 2017
> Python on windows slaves
> -------------------------
>
> Key: JBIDE-24883
> URL: https://issues.jboss.org/browse/JBIDE-24883
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Reporter: Pavol Srna
> Assignee: Pavol Srna
> Labels: central-ci
> Fix For: 4.5.1.AM2
>
>
> python installation needs to be scripted in mwqa-cloud-slaves to be installed automatically when provisioning from openstack.
> Purpose: facilitate running cross-platform scripts (eg., for JDK detection & discovery). Will allow Nick to start porting .sh script to .py so they can be used on all OSes.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-3868) Document (and check) required disk space before beginning install
by Mohit Suman (JIRA)
[ https://issues.jboss.org/browse/JBDS-3868?page=com.atlassian.jira.plugin.... ]
Mohit Suman updated JBDS-3868:
------------------------------
Sprint: (was: devex #136 August 2017)
> Document (and check) required disk space before beginning install
> -----------------------------------------------------------------
>
> Key: JBDS-3868
> URL: https://issues.jboss.org/browse/JBDS-3868
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit
> Reporter: Robert Terzi
> Assignee: Mohit Suman
> Priority: Minor
> Labels: ui
> Fix For: 11.x
>
>
> The installer and it's documentation should indicate the minimum required disk space before beginning the download and installation process.
> Between temporary files, and download/installs going on in parallel. I'm guessing at least 10-15 GB free is needed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4411) DevSuite 1.4 installer display required disk space
by Mohit Suman (JIRA)
[ https://issues.jboss.org/browse/JBDS-4411?page=com.atlassian.jira.plugin.... ]
Mohit Suman updated JBDS-4411:
------------------------------
Sprint: (was: devex #136 August 2017)
> DevSuite 1.4 installer display required disk space
> ---------------------------------------------------
>
> Key: JBDS-4411
> URL: https://issues.jboss.org/browse/JBDS-4411
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Environment: DevSuite 1.4 installer, Windows 10 Pro/64
> Reporter: Robert Terzi
> Assignee: Mohit Suman
> Priority: Minor
> Labels: ui
> Fix For: 11.x
>
> Attachments: install-size.png
>
>
> DevSuite 1.4 installer (online) should display the disk space requirements which should include the calculation for both the downloads and the unpacked/installed files.
> As a user,
> I would like to know the disk space required to complete the installation before starting
> so that I have an idea whether the installation can be completed successfully.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24873) Add management itests to eap jbds compatibility jenkins job
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24873?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-24873 at 8/29/17 5:49 AM:
----------------------------------------------------------------
I managed to get the maven call to work to the extent that it actually starts the tests. But the tests fail.
First issue is that they're looking for java 7 which they shouldn't:
{code}
09:12:35 testJava7HomeSet(org.jboss.tools.as.management.itests.VerifyJREFlagsTest) Time elapsed: 0.398 sec <<< FAILURE!
09:12:35 junit.framework.AssertionFailedError: Java 7 version string must start with 1.7: 1.8.0_121
09:12:35 at junit.framework.Assert.fail(Assert.java:57)
09:12:35 at junit.framework.Assert.assertTrue(Assert.java:22)
09:12:35 at junit.framework.TestCase.assertTrue(TestCase.java:192)
09:12:35 at org.jboss.tools.as.management.itests.VerifyJREFlagsTest.testJava7HomeSet(VerifyJREFlagsTest.java:59)
{code}
Also, for some reason it's looking for jboss-as-7 for example:
{code}
09:12:35 junit.framework.AssertionFailedError: /home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af/as/itests/org.jboss.tools.as.management.itests/target/requirements/jboss-as-7.0.0.Final does not exist.
09:12:35 at junit.framework.Assert.fail(Assert.java:57)
09:12:35 at junit.framework.Assert.assertTrue(Assert.java:22)
09:12:35 at org.jboss.tools.as.management.itests.AS7ManagementServicePreReqTest.verifyCorrectService(AS7ManagementServicePreReqTest.java:37)
{code}
This was the maven call used:
{code}
mvn -f /home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af/as/itests/org.jboss.tools.as.management.itests/pom.xml -DDEVSTUDIO_REPO=https://devstudio.redhat.com/11/stable/updates/ "-DMVN_ADDITIONAL_PARAMS=-s /home/hudson/.m2/settings_jbds.xml" -Djdk=oracle-java-1.8 -DEAP_VERSION=7.1.0.CR1 -DJBDS_VERSION=11_x "-Dlabel=RHEL7 && x86_64" -Djbosstools.test.jboss.home.7.1=/home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af"/as/itests/org.jboss.tools.as.ui.bot.itests/target/requirements/"jboss-eap-7.1 -Djbosstools.test.singleruntime.location=/home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af"/as/itests/org.jboss.tools.as.ui.bot.itests/target/requirements/"jboss-eap-7.1 -Ddownload.cache.directory=/home/hudson/static_build_env/jbds/download-cache -Djbosstools.test.jboss-eap-7.x.md5=14e4f8853111086962fa042a4d3cf1d2 -Dswtbot.test.skip=false -Djbosstools.test.jboss-eap-7.x.home=jboss-eap-7.1 -DskipRequirements=false -DdevstudioRepository=https://devstudio.redhat.com/11/stable/updates/ -Djbosstools.test.jboss-eap-7.x.url=file:///home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af/eap7.zip -DadditionalProperties="-Djbosstools.test.single.runtime.location="/home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af"/as/itests/org.jboss.tools.as.ui.bot.itests/target/requirements/"jboss-eap-7.1 -Djbosstools.test.jre.8=/qa/tools/opt/x86_64/jdk1.8.0_last -Dtest.profile=eap7x-compatibility -Dusage_reporting_enabled=false -Dmaven.test.failure.ignore=true -Dmaven.repo.local=/home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af/.repository clean verify -PITests,download-devstudio -e -s /home/hudson/.m2/settings_jbds.xml
{code}
Some of the parameters are redundant there - there are copied from the other maven call. I can remove some later. But I do have the parameters that you said were needed.
[~rob.stryker], can you take a look?
The job is here:
https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7x-jbds-co...
The results are green because I haven't configure the job to look for these new test results yet.
was (Author: mmalina):
I managed to get the maven call to work to the extent that it actually starts the tests. But the tests fail.
First issue is that they're looking for java 7 which they shouldn't:
{code}
09:12:35 testJava7HomeSet(org.jboss.tools.as.management.itests.VerifyJREFlagsTest) Time elapsed: 0.398 sec <<< FAILURE!
09:12:35 junit.framework.AssertionFailedError: Java 7 version string must start with 1.7: 1.8.0_121
09:12:35 at junit.framework.Assert.fail(Assert.java:57)
09:12:35 at junit.framework.Assert.assertTrue(Assert.java:22)
09:12:35 at junit.framework.TestCase.assertTrue(TestCase.java:192)
09:12:35 at org.jboss.tools.as.management.itests.VerifyJREFlagsTest.testJava7HomeSet(VerifyJREFlagsTest.java:59)
{code}
Also, for some reason it's looking for jboss-as-7 for example:
{code}
09:12:35 junit.framework.AssertionFailedError: /home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af/as/itests/org.jboss.tools.as.management.itests/target/requirements/jboss-as-7.0.0.Final does not exist.
09:12:35 at junit.framework.Assert.fail(Assert.java:57)
09:12:35 at junit.framework.Assert.assertTrue(Assert.java:22)
09:12:35 at org.jboss.tools.as.management.itests.AS7ManagementServicePreReqTest.verifyCorrectService(AS7ManagementServicePreReqTest.java:37)
{code}
This was the maven call used:
{code}
mvn -f /home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af/as/itests/org.jboss.tools.as.management.itests/pom.xml -DDEVSTUDIO_REPO=https://devstudio.redhat.com/11/stable/updates/ "-DMVN_ADDITIONAL_PARAMS=-s /home/hudson/.m2/settings_jbds.xml" -Djdk=oracle-java-1.8 -DEAP_VERSION=7.1.0.CR1 -DJBDS_VERSION=11_x "-Dlabel=RHEL7 && x86_64" -Djbosstools.test.jboss.home.7.1=/home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af"/as/itests/org.jboss.tools.as.ui.bot.itests/target/requirements/"jboss-eap-7.1 -Djbosstools.test.singleruntime.location=/home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af"/as/itests/org.jboss.tools.as.ui.bot.itests/target/requirements/"jboss-eap-7.1 -Ddownload.cache.directory=/home/hudson/static_build_env/jbds/download-cache -Djbosstools.test.jboss-eap-7.x.md5=14e4f8853111086962fa042a4d3cf1d2 -Dswtbot.test.skip=false -Djbosstools.test.jboss-eap-7.x.home=jboss-eap-7.1 -DskipRequirements=false -DdevstudioRepository=https://devstudio.redhat.com/11/stable/updates/ -Djbosstools.test.jboss-eap-7.x.url=file:///home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af/eap7.zip -DadditionalProperties="-Djbosstools.test.single.runtime.location="/home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af"/as/itests/org.jboss.tools.as.ui.bot.itests/target/requirements/"jboss-eap-7.1 -Djbosstools.test.jre.8=/qa/tools/opt/x86_64/jdk1.8.0_last -Dtest.profile=eap7x-compatibility -Dusage_reporting_enabled=false -Dmaven.test.failure.ignore=true -Dmaven.repo.local=/home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af/.repository clean verify -PITests,download-devstudio -e -s /home/hudson/.m2/settings_jbds.xml
{code}
Some of the parameters are redundant there - there are copied from the other maven call. I can remove some later. But I do have the parameters that you said were needed.
[~rob.stryker], can you take a look?
> Add management itests to eap jbds compatibility jenkins job
> -----------------------------------------------------------
>
> Key: JBIDE-24873
> URL: https://issues.jboss.org/browse/JBIDE-24873
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.5.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
>
> The EAP team would like us to add this test
> org.jboss.tools.as.management.itests
> to their compatibility job:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP...
> details here: EAP7-194
> The test to be added is run here:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Cc: [~rob.stryker]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24873) Add management itests to eap jbds compatibility jenkins job
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24873?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24873:
---------------------------------------
I managed to get the maven call to work to the extent that it actually starts the tests. But the tests fail.
First issue is that they're looking for java 7 which they shouldn't:
{code}
09:12:35 testJava7HomeSet(org.jboss.tools.as.management.itests.VerifyJREFlagsTest) Time elapsed: 0.398 sec <<< FAILURE!
09:12:35 junit.framework.AssertionFailedError: Java 7 version string must start with 1.7: 1.8.0_121
09:12:35 at junit.framework.Assert.fail(Assert.java:57)
09:12:35 at junit.framework.Assert.assertTrue(Assert.java:22)
09:12:35 at junit.framework.TestCase.assertTrue(TestCase.java:192)
09:12:35 at org.jboss.tools.as.management.itests.VerifyJREFlagsTest.testJava7HomeSet(VerifyJREFlagsTest.java:59)
{code}
Also, for some reason it's looking for jboss-as-7 for example:
{code}
09:12:35 junit.framework.AssertionFailedError: /home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af/as/itests/org.jboss.tools.as.management.itests/target/requirements/jboss-as-7.0.0.Final does not exist.
09:12:35 at junit.framework.Assert.fail(Assert.java:57)
09:12:35 at junit.framework.Assert.assertTrue(Assert.java:22)
09:12:35 at org.jboss.tools.as.management.itests.AS7ManagementServicePreReqTest.verifyCorrectService(AS7ManagementServicePreReqTest.java:37)
{code}
This was the maven call used:
{code}
mvn -f /home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af/as/itests/org.jboss.tools.as.management.itests/pom.xml -DDEVSTUDIO_REPO=https://devstudio.redhat.com/11/stable/updates/ "-DMVN_ADDITIONAL_PARAMS=-s /home/hudson/.m2/settings_jbds.xml" -Djdk=oracle-java-1.8 -DEAP_VERSION=7.1.0.CR1 -DJBDS_VERSION=11_x "-Dlabel=RHEL7 && x86_64" -Djbosstools.test.jboss.home.7.1=/home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af"/as/itests/org.jboss.tools.as.ui.bot.itests/target/requirements/"jboss-eap-7.1 -Djbosstools.test.singleruntime.location=/home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af"/as/itests/org.jboss.tools.as.ui.bot.itests/target/requirements/"jboss-eap-7.1 -Ddownload.cache.directory=/home/hudson/static_build_env/jbds/download-cache -Djbosstools.test.jboss-eap-7.x.md5=14e4f8853111086962fa042a4d3cf1d2 -Dswtbot.test.skip=false -Djbosstools.test.jboss-eap-7.x.home=jboss-eap-7.1 -DskipRequirements=false -DdevstudioRepository=https://devstudio.redhat.com/11/stable/updates/ -Djbosstools.test.jboss-eap-7.x.url=file:///home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af/eap7.zip -DadditionalProperties="-Djbosstools.test.single.runtime.location="/home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af"/as/itests/org.jboss.tools.as.ui.bot.itests/target/requirements/"jboss-eap-7.1 -Djbosstools.test.jre.8=/qa/tools/opt/x86_64/jdk1.8.0_last -Dtest.profile=eap7x-compatibility -Dusage_reporting_enabled=false -Dmaven.test.failure.ignore=true -Dmaven.repo.local=/home/hudson/hudson_workspace/workspace/eap-7x-jbds-compatibility-jbosstools-4.5.x-RHEL/f96458af/.repository clean verify -PITests,download-devstudio -e -s /home/hudson/.m2/settings_jbds.xml
{code}
Some of the parameters are redundant there - there are copied from the other maven call. I can remove some later. But I do have the parameters that you said were needed.
[~rob.stryker], can you take a look?
> Add management itests to eap jbds compatibility jenkins job
> -----------------------------------------------------------
>
> Key: JBIDE-24873
> URL: https://issues.jboss.org/browse/JBIDE-24873
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.5.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
>
> The EAP team would like us to add this test
> org.jboss.tools.as.management.itests
> to their compatibility job:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP...
> details here: EAP7-194
> The test to be added is run here:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Cc: [~rob.stryker]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months