[JBoss JIRA] (JBTIS-1149) Cannot add Fuse server
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1149?page=com.atlassian.jira.plugin... ]
Brian Fitzpatrick commented on JBTIS-1149:
------------------------------------------
Merged https://github.com/jboss-switchyard/tools/pull/680
> Cannot add Fuse server
> ----------------------
>
> Key: JBTIS-1149
> URL: https://issues.jboss.org/browse/JBTIS-1149
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE, switchyard
> Affects Versions: 11.0.0.CR1
> Environment: devstudio-integration-stack-11.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Brian Fitzpatrick
> Priority: Blocker
> Fix For: 11.0.0.CR2
>
> Attachments: sy_fuse_server.png
>
>
> The SwitchYard tooling should support WildFly/EAP and Karaf/Fuse servers. But it seems that the Fuse server plugins are not correctly installed together with the Switchyard and therefore we cannot create a Fuse server.
> EDIT: We need to install the feature *org.fusesource.ide.server.extensions.feature* which is available in the target platform
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBTIS-1149) Cannot add Fuse server
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1149?page=com.atlassian.jira.plugin... ]
Brian Fitzpatrick updated JBTIS-1149:
-------------------------------------
Fix Version/s: 11.0.0.CR2
> Cannot add Fuse server
> ----------------------
>
> Key: JBTIS-1149
> URL: https://issues.jboss.org/browse/JBTIS-1149
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE, switchyard
> Affects Versions: 11.0.0.CR1
> Environment: devstudio-integration-stack-11.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Brian Fitzpatrick
> Priority: Blocker
> Fix For: 11.0.0.CR2
>
> Attachments: sy_fuse_server.png
>
>
> The SwitchYard tooling should support WildFly/EAP and Karaf/Fuse servers. But it seems that the Fuse server plugins are not correctly installed together with the Switchyard and therefore we cannot create a Fuse server.
> EDIT: We need to install the feature *org.fusesource.ide.server.extensions.feature* which is available in the target platform
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-22799) Create integration tests PR check job for server
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22799?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22799:
------------------------------------
Looks like the slave on which the job is now running DOES have all 4 JDKs available. Here are the 4 Oracle JDKs being used:
{code}
13:37:53 + echo jbosstoolstestjre5=/qa/tools/opt/x86_64/jdk1.5.0_last
13:37:53 java version "1.5.0_22"
13:37:53 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
13:37:53 Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_22-b03, mixed mode)
13:37:53 + echo jbosstoolstestjre6=/qa/tools/opt/x86_64/jdk1.6.0_last
13:37:54 java version "1.6.0_45"
13:37:54 Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
13:37:54 Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
13:37:54 + echo jbosstoolstestjre7=/qa/tools/opt/x86_64/jdk1.7.0_last
13:37:55 java version "1.7.0_79"
13:37:55 Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
13:37:55 Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)
13:37:55 + echo jbosstoolstestjre8=/qa/tools/opt/x86_64/jdk1.8.0_last
13:37:55 java version "1.8.0_121"
13:37:55 Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
13:37:55 Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode){code}
> Create integration tests PR check job for server
> ------------------------------------------------
>
> Key: JBIDE-22799
> URL: https://issues.jboss.org/browse/JBIDE-22799
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, qa
> Reporter: Rastislav Wagner
> Assignee: Martin Malina
> Fix For: 4.5.0.Final
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24682) Reflect changes in minishift's version command
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24682?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-24682:
---------------------------------------
[~rob.stryker][~hardy.ferentschik] thanks guys for taking swift action in this issue. I am checking progress and I am ready to test bits right away at the time when they are out (cdk nightly build and Rob's PR reflecting changes in minishift version command.
I am thinking of dedicating one jenkins job base on nightly CDK builds that could be incorporated in CKD nightly build pipeline. [~hardy.ferentschik] You already talked about it on previous meetings and as soon as https://issues.jboss.org/browse/JBIDE-24656 is done, I will be able to provide this hopefully-fast and stable basic smoke test job of cdk integration in devstudio to you and so, we would have end-to-end pipeline for cdk, that would catch such tooling breakages asap.
> Reflect changes in minishift's version command
> ----------------------------------------------
>
> Key: JBIDE-24682
> URL: https://issues.jboss.org/browse/JBIDE-24682
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.0.Final
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.5.0.Final
>
>
> Due to changes in upstream project the 'minishift version' command returns different lines.
> CDK result from http://cdk-builds.usersys.redhat.com/builds/weekly/19-Jun-2017.cdk-3.0.0-... build:
> {code}
> Minishift version: 1.0.0+4f8cb6d
> CDK Version: 3.0.0-2
> {code}
> vs.
> CDK result from nightly http://cdk-builds.usersys.redhat.com/builds/nightly/13-Jul-2017 build:
> {code}
> minishift v1.2.0+001371f
> CDK Version:3.0.0-13072017-1
> {code}
> And this change results in error while creating CDK 3 server adapter with newer CDK nightly build as it ends with "Unknown error while checking minishift version" as we expect the string to contains "Minishift Version".
> We should get in touch with cdk team to check whether they plan to change the output 'CDK Version' to something else as well, in case we are going to distinguish between minishift and cdk. If we accept in CDK 3 server adapter both cdk and minishift binary maybe we should create a CDK jira that would ask for changing output from 'minishift version' from 'CDK Version: X.X.X' to 'cdk vX.X.X'. I do not know if we plan to do so, it is just an idea...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-22799) Create integration tests PR check job for server
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22799?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22799 at 7/24/17 9:37 AM:
-------------------------------------------------------------
Meanwhile... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is no longer failing. There are test failures being reported, but the job's yellow instead of red.
I suspect this could be that the job is running with invalid test.jre properties:
{code}
/mnt/hudson_workspace/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.9/bin/mvn \
-Ddownload.cache.directory=/home/hudson/static_build_env/devstudio/download-cache \
-DJOB_NAME=jbosstools-server-Run-Unit-and-ITests_master -DBUILD_NUMBER=380 \
-DskipPrivateRequirements=false \
-Djbosstools.test.jre.8=/qa/tools/opt/x86_64/jdk1.8.0_last \
-Djbosstools.test.jre.7=/qa/tools/opt/x86_64/jdk1.7.0_last \
-Djbosstools.test.jre.6=/qa/tools/opt/x86_64/jdk1.6.0_last \
-Djbosstools.test.jre.5=/qa/tools/opt/x86_64/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-Run-Unit-and-ITests_master/.repository \
clean install -B -U -fae -e -P hudson,pack200,unified.target,maximum{code}
[~rob.stryker] can you run the same tests locally (with similar local settings) and see if you get the same failures?
We could purge the .repository and download-cache folders and see if we get better results. Or use `-DskipPrivateRequirements=true` ?
Meanwhile I've updated the job [1] to show exactly what's being used for the jre properties, removed commented blocks, and reordered the steps.
[1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... (see line 118)
Respinning:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=381
was (Author: nickboldt):
Meanwhile... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is no longer failing. There are test failures being reported, but the job's yellow instead of red.
I suspect this could be that the job is running with invalid test.jre properties:
{code}
/mnt/hudson_workspace/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.9/bin/mvn \
-Ddownload.cache.directory=/home/hudson/static_build_env/devstudio/download-cache \
-DJOB_NAME=jbosstools-server-Run-Unit-and-ITests_master -DBUILD_NUMBER=380 \
-DskipPrivateRequirements=false \
-Djbosstools.test.jre.8=/qa/tools/opt/x86_64/jdk1.8.0_last \
-Djbosstools.test.jre.7=/qa/tools/opt/x86_64/jdk1.7.0_last \
-Djbosstools.test.jre.6=/qa/tools/opt/x86_64/jdk1.6.0_last \
-Djbosstools.test.jre.5=/qa/tools/opt/x86_64/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-Run-Unit-and-ITests_master/.repository \
clean install -B -U -fae -e -P hudson,pack200,unified.target,maximum{code}
[~rob.stryker] can you run the same tests locally (with similar local settings) and see if you get the same failures?
We could purge the .repository and download-cache folders and see if we get better results. Or use `-DskipPrivateRequirements=true` ?
Meanwhile I've updated the job [1] to show exactly what's being used for the jre properties, removed commented blocks, and reordered the steps.
[1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... (see line 118)
> Create integration tests PR check job for server
> ------------------------------------------------
>
> Key: JBIDE-22799
> URL: https://issues.jboss.org/browse/JBIDE-22799
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, qa
> Reporter: Rastislav Wagner
> Assignee: Martin Malina
> Fix For: 4.5.0.Final
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-22799) Create integration tests PR check job for server
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22799?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22799:
------------------------------------
Meanwhile... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is no longer failing. There are test failures being reported, but the job's yellow instead of red.
I suspect this could be that the job is running with invalid test.jre properties:
{code}
/mnt/hudson_workspace/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.9/bin/mvn \
-Ddownload.cache.directory=/home/hudson/static_build_env/devstudio/download-cache \
-DJOB_NAME=jbosstools-server-Run-Unit-and-ITests_master -DBUILD_NUMBER=380 \
-DskipPrivateRequirements=false \
-Djbosstools.test.jre.8=/qa/tools/opt/x86_64/jdk1.8.0_last \
-Djbosstools.test.jre.7=/qa/tools/opt/x86_64/jdk1.7.0_last \
-Djbosstools.test.jre.6=/qa/tools/opt/x86_64/jdk1.6.0_last \
-Djbosstools.test.jre.5=/qa/tools/opt/x86_64/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-Run-Unit-and-ITests_master/.repository \
clean install -B -U -fae -e -P hudson,pack200,unified.target,maximum{code}
[~rob.stryker] can you run the same tests locally (with similar local settings) and see if you get the same failures?
We could purge the .repository and download-cache folders and see if we get better results. Or use `-DskipPrivateRequirements=true` ?
Meanwhile I've updated the job [1] to show exactly what's being used for the jre properties, removed commented blocks, and reordered the steps.
[1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... (see line 118)
> Create integration tests PR check job for server
> ------------------------------------------------
>
> Key: JBIDE-22799
> URL: https://issues.jboss.org/browse/JBIDE-22799
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, qa
> Reporter: Rastislav Wagner
> Assignee: Martin Malina
> Fix For: 4.5.0.Final
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBTIS-1149) Cannot add Fuse server
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1149?page=com.atlassian.jira.plugin... ]
Brian Fitzpatrick commented on JBTIS-1149:
------------------------------------------
Created https://github.com/jboss-switchyard/tools/pull/680
> Cannot add Fuse server
> ----------------------
>
> Key: JBTIS-1149
> URL: https://issues.jboss.org/browse/JBTIS-1149
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE, switchyard
> Affects Versions: 11.0.0.CR1
> Environment: devstudio-integration-stack-11.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Brian Fitzpatrick
> Priority: Blocker
> Attachments: sy_fuse_server.png
>
>
> The SwitchYard tooling should support WildFly/EAP and Karaf/Fuse servers. But it seems that the Fuse server plugins are not correctly installed together with the Switchyard and therefore we cannot create a Fuse server.
> EDIT: We need to install the feature *org.fusesource.ide.server.extensions.feature* which is available in the target platform
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-16161) Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned)
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16161:
----------------------------------------
I'm not sure just having the capability does immediately cascade to p2 and Tycho properly resolving the dependency. So it requires testing first.
> Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-16161
> URL: https://issues.jboss.org/browse/JBIDE-16161
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, upstream
> Affects Versions: 4.2.0.Alpha2
> Reporter: Snjezana Peco
> Assignee: Mickael Istria
> Fix For: 4.3.x, 4.5.x
>
>
> Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin.
> The easiest way is to add the org.eclipse.e4.rcp feature to the main build.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBTIS-1149) Cannot add Fuse server
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1149?page=com.atlassian.jira.plugin... ]
Paul Leacu reassigned JBTIS-1149:
---------------------------------
Assignee: Brian Fitzpatrick
> Cannot add Fuse server
> ----------------------
>
> Key: JBTIS-1149
> URL: https://issues.jboss.org/browse/JBTIS-1149
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE, switchyard
> Affects Versions: 11.0.0.CR1
> Environment: devstudio-integration-stack-11.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Brian Fitzpatrick
> Priority: Blocker
> Attachments: sy_fuse_server.png
>
>
> The SwitchYard tooling should support WildFly/EAP and Karaf/Fuse servers. But it seems that the Fuse server plugins are not correctly installed together with the Switchyard and therefore we cannot create a Fuse server.
> EDIT: We need to install the feature *org.fusesource.ide.server.extensions.feature* which is available in the target platform
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months