January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23733: ------------------------------------ Ah, OK, that makes sense. So then the value I would pass to the child jobs would be the version in the staging updates site, which today is simply 10.3.0.AM2. Or do you want the version of the latest INSTALLER jar, which is 10.3.0.AM2-v20170127-1155-B6970 ? > Merge .smoke and .nightly integration jobs into a single job and run them weekly > -------------------------------------------------------------------------------- > > Key: JBIDE-23733 > URL: https://issues.jboss.org/browse/JBIDE-23733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > Attachments: Screenshot from 2017-01-31 17-09-00.png > > > Purpose: > a) easier maintenance of jobs / tests > b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests > c) more frequent full integration runs (rather than once per sprint, once per week) > Tests to merge are in this view: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-23733: ------------------------------------- Attachment: Screenshot from 2017-01-31 17-09-00.png > Merge .smoke and .nightly integration jobs into a single job and run them weekly > -------------------------------------------------------------------------------- > > Key: JBIDE-23733 > URL: https://issues.jboss.org/browse/JBIDE-23733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > Attachments: Screenshot from 2017-01-31 17-09-00.png > > > Purpose: > a) easier maintenance of jobs / tests > b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests > c) more frequent full integration runs (rather than once per sprint, once per week) > Tests to merge are in this view: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-23733: ------------------------------------------ I dont use the variable anywhere in the actual build. Its purpose is purely for setting a description for a build - see the screenshot !Screenshot from 2017-01-31 17-09-00.png|thumbnail! > Merge .smoke and .nightly integration jobs into a single job and run them weekly > -------------------------------------------------------------------------------- > > Key: JBIDE-23733 > URL: https://issues.jboss.org/browse/JBIDE-23733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > Attachments: Screenshot from 2017-01-31 17-09-00.png > > > Purpose: > a) easier maintenance of jobs / tests > b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests > c) more frequent full integration runs (rather than once per sprint, once per week) > Tests to merge are in this view: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23816) Cannot run server itest module separately

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23816?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23816: --------------------------------------- [~nickboldt], I'm quite fine using the download-devstudio profile, actually that's what I want - to test against devstudio. (So redefining devstudioRepository to point to the jbt repo is not an option.) But the devstudio repo still does not include the missing as.reddeer bundle, so I still need to get that somewhere. Rasto suggested I add the coretests repo to the ITests profile in the parent pom, like this: https://github.com/jbosstools/jbosstools-build/pull/244 Would that be acceptable for you? > Cannot run server itest module separately > ----------------------------------------- > > Key: JBIDE-23816 > URL: https://issues.jboss.org/browse/JBIDE-23816 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, server > Affects Versions: 4.4.3.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.3.Final > > > Now that the server tools bot tests have been moved from jbosstools-integration-tests github repo to jbosstools-server, I would like to find a way to run a specific test in the simplest way possible. > The test bundle I want to run is this: > as/itests/org.jboss.tools.as.ui.bot.itests [1] > This is the kind of command that I would expect to work from the root directory of the git repo: > {code}$ mvn clean verify -pl as/itests/org.jboss.tools.as.ui.bot.itests -am -Djbosstools.test.jboss-eap-7.x.md5=4973998216a8eb5b2f5a6fc00d84705c -Dswtbot.test.skip=false -Djbosstools.test.jboss-eap-7.x.home='${requirementsDirectory}/jboss-eap-7.1' -DskipRequirements=false -Djbosstools.test.jboss-eap-7.x.url=$EAP_URL -Dtest.profile=eap7x-compatibility -Dusage_reporting_enabled=false -U -DskipTests=false -PITests{code} > This will fail: > {code} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.as.ui.bot.itests 3.2.3.qualifier > [ERROR] Missing requirement: org.jboss.tools.as.ui.bot.itests 3.2.3.qualifier requires 'bundle org.jboss.ide.eclipse.as.reddeer > {code} > I was under the impression that using "-pl -am" with maven will ensure that all the deps from the maven project are added to the build, but it seems this does not work for dependencies defined in Manifest.MF file of the bundle? > What options do we have here? The simplest solution is to first build the whole repo and install it in the local maven repo, but I'd like to avoid that. Another option would be to add the whole jbosstools repo to the ITests profile in parent pom, but I'm guessing that not everybody would like that. > Is there some other way? > [1] https://github.com/jbosstools/jbosstools-server/tree/master/as/itests/org... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23733: ------------------------------------ b) I saw it in the DSL, but I don't see in browsersim.it.smoke job where DEVSTUDIO_VERSION variable is used. Also doesn't appear in the console log. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/browsers... So... how are you passing it to the child jobs, and how are you using it? If you're downloading from /staging/updates you'll just pull the latest from the update site -- no need to specify a version. And if you're pulling from /snapshots/builds or /staging/builds, there's a latest symlink you can use which doesn't require a version either. > Merge .smoke and .nightly integration jobs into a single job and run them weekly > -------------------------------------------------------------------------------- > > Key: JBIDE-23733 > URL: https://issues.jboss.org/browse/JBIDE-23733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > > Purpose: > a) easier maintenance of jobs / tests > b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests > c) more frequent full integration runs (rather than once per sprint, once per week) > Tests to merge are in this view: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23814) Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error

by Siamak Sadeghianfar (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23814?page=com.atlassian.jira.plugi... ] Siamak Sadeghianfar edited comment on JBIDE-23814 at 1/31/17 10:56 AM: ----------------------------------------------------------------------- Versions I used: oc v3.4.0.40 kubernetes v1.4.0+776c994 features: Basic-Auth openshift v3.3.1.9 kubernetes v1.3.0+52492b4 was (Author: ssadeghi): Versions I used: oc v3.4.0.40 kubernetes v1.4.0+776c994 features: Basic-Auth Server https://api.ded-stage-aws.openshift.com:443 openshift v3.3.1.9 kubernetes v1.3.0+52492b4 > Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error > ----------------------------------------------------------------- > > Key: JBIDE-23814 > URL: https://issues.jboss.org/browse/JBIDE-23814 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: Red Hat JBoss Developer Studio > Version: 10.2.0.GA > Build id: GA-v20161125-1418-B55 > Build date: 20161125-1418 > JBoss Openshift UI Plugin > Version: 3.3.1.v20161125-0956 > OpenShift > openshift v3.3.1.3 > Reporter: Siamak Sadeghianfar > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.3.Final > > Attachments: jboss-eap70-openshift.png > > > When adding a Server Adapter for an JBoss EAP 7 based deployments on OpenShift, operation fails with this error: > {{Could not sync /private/tmp/workspace-demo/.metadata/.plugins/org.jboss.ide.eclipse.as.core/inventory-dev-ssadeghi@inventory/deploy to all pods running the service inventory > OpenShiftBinaryCapability process exited: error: auth info "ssadeghi-redhat.com" does not exist}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23814) Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error

by Siamak Sadeghianfar (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23814?page=com.atlassian.jira.plugi... ] Siamak Sadeghianfar commented on JBIDE-23814: --------------------------------------------- Versions I used: oc v3.4.0.40 kubernetes v1.4.0+776c994 features: Basic-Auth Server https://api.ded-stage-aws.openshift.com:443 openshift v3.3.1.9 kubernetes v1.3.0+52492b4 > Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error > ----------------------------------------------------------------- > > Key: JBIDE-23814 > URL: https://issues.jboss.org/browse/JBIDE-23814 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: Red Hat JBoss Developer Studio > Version: 10.2.0.GA > Build id: GA-v20161125-1418-B55 > Build date: 20161125-1418 > JBoss Openshift UI Plugin > Version: 3.3.1.v20161125-0956 > OpenShift > openshift v3.3.1.3 > Reporter: Siamak Sadeghianfar > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.3.Final > > Attachments: jboss-eap70-openshift.png > > > When adding a Server Adapter for an JBoss EAP 7 based deployments on OpenShift, operation fails with this error: > {{Could not sync /private/tmp/workspace-demo/.metadata/.plugins/org.jboss.ide.eclipse.as.core/inventory-dev-ssadeghi@inventory/deploy to all pods running the service inventory > OpenShiftBinaryCapability process exited: error: auth info "ssadeghi-redhat.com" does not exist}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23659) integrationt-tests: LogsTest is failing and cannot run individually

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23659?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-23659. ------------------------------ > integrationt-tests: LogsTest is failing and cannot run individually > ------------------------------------------------------------------- > > Key: JBIDE-23659 > URL: https://issues.jboss.org/browse/JBIDE-23659 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.AM2 > > > LogsTest cannot run individually, it relies on prior tests to create an EAP application in OpenShift. > Furthermore it is currently failing because of JBIDE-23622 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23816) Cannot run server itest module separately

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23816?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23816: ------------------------------------ If you don't like that the download-devstudio profile does extra work to create a target platform, we could create a new profile that simply enables the snapshot site repo (or the jbosstools-server update site) in the jbosstools-server root pom, which can then be selectively enabled when running a jbostools-server itest. > Cannot run server itest module separately > ----------------------------------------- > > Key: JBIDE-23816 > URL: https://issues.jboss.org/browse/JBIDE-23816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, server > Affects Versions: 4.4.3.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.3.Final > > > Now that the server tools bot tests have been moved from jbosstools-integration-tests github repo to jbosstools-server, I would like to find a way to run a specific test in the simplest way possible. > The test bundle I want to run is this: > as/itests/org.jboss.tools.as.ui.bot.itests [1] > This is the kind of command that I would expect to work from the root directory of the git repo: > {code}$ mvn clean verify -pl as/itests/org.jboss.tools.as.ui.bot.itests -am -Djbosstools.test.jboss-eap-7.x.md5=4973998216a8eb5b2f5a6fc00d84705c -Dswtbot.test.skip=false -Djbosstools.test.jboss-eap-7.x.home='${requirementsDirectory}/jboss-eap-7.1' -DskipRequirements=false -Djbosstools.test.jboss-eap-7.x.url=$EAP_URL -Dtest.profile=eap7x-compatibility -Dusage_reporting_enabled=false -U -DskipTests=false -PITests{code} > This will fail: > {code} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.as.ui.bot.itests 3.2.3.qualifier > [ERROR] Missing requirement: org.jboss.tools.as.ui.bot.itests 3.2.3.qualifier requires 'bundle org.jboss.ide.eclipse.as.reddeer > {code} > I was under the impression that using "-pl -am" with maven will ensure that all the deps from the maven project are added to the build, but it seems this does not work for dependencies defined in Manifest.MF file of the bundle? > What options do we have here? The simplest solution is to first build the whole repo and install it in the local maven repo, but I'd like to avoid that. Another option would be to add the whole jbosstools repo to the ITests profile in parent pom, but I'm guessing that not everybody would like that. > Is there some other way? > [1] https://github.com/jbosstools/jbosstools-server/tree/master/as/itests/org... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23816) Cannot run server itest module separately

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23816?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23816: ------------------------------- Issue Type: Feature Request (was: Bug) > Cannot run server itest module separately > ----------------------------------------- > > Key: JBIDE-23816 > URL: https://issues.jboss.org/browse/JBIDE-23816 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, server > Affects Versions: 4.4.3.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.3.Final > > > Now that the server tools bot tests have been moved from jbosstools-integration-tests github repo to jbosstools-server, I would like to find a way to run a specific test in the simplest way possible. > The test bundle I want to run is this: > as/itests/org.jboss.tools.as.ui.bot.itests [1] > This is the kind of command that I would expect to work from the root directory of the git repo: > {code}$ mvn clean verify -pl as/itests/org.jboss.tools.as.ui.bot.itests -am -Djbosstools.test.jboss-eap-7.x.md5=4973998216a8eb5b2f5a6fc00d84705c -Dswtbot.test.skip=false -Djbosstools.test.jboss-eap-7.x.home='${requirementsDirectory}/jboss-eap-7.1' -DskipRequirements=false -Djbosstools.test.jboss-eap-7.x.url=$EAP_URL -Dtest.profile=eap7x-compatibility -Dusage_reporting_enabled=false -U -DskipTests=false -PITests{code} > This will fail: > {code} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.as.ui.bot.itests 3.2.3.qualifier > [ERROR] Missing requirement: org.jboss.tools.as.ui.bot.itests 3.2.3.qualifier requires 'bundle org.jboss.ide.eclipse.as.reddeer > {code} > I was under the impression that using "-pl -am" with maven will ensure that all the deps from the maven project are added to the build, but it seems this does not work for dependencies defined in Manifest.MF file of the bundle? > What options do we have here? The simplest solution is to first build the whole repo and install it in the local maven repo, but I'd like to avoid that. Another option would be to add the whole jbosstools repo to the ITests profile in parent pom, but I'm guessing that not everybody would like that. > Is there some other way? > [1] https://github.com/jbosstools/jbosstools-server/tree/master/as/itests/org... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2017