November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23384) Include integration-tests (update site only) in staging and stable update sites

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23384?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23384: --------------------------------------- I can see the staging update site here, so that's good: http://download.jboss.org/jbosstools/neon/staging/updates/integration-tes... What is not so good is the fact that the update site is from November 1st. That's probably because running all of the tests was enabled in jenkins and it still doesn't just work - people run their tests in various ways. There is an effort by Jeff (with help of QE) to make this work. But until it does, I disabled the tests in the job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... I kicked off a build and hopefully it will work. Once the stable update sites are created, I will check integration-tests repo is copied there (but it will still be the old update site that is currently seen on staging) and then close this JIRA. > Include integration-tests (update site only) in staging and stable update sites > ------------------------------------------------------------------------------- > > Key: JBIDE-23384 > URL: https://issues.jboss.org/browse/JBIDE-23384 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.2.Final > > > This will allow us the use case of running integration tests against the latest release of devstudio. This use case is required by EAP QE running our tests against their EAP development builds. > Currently we have this repo: > http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t... > We're referencing it from our root pom: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > And set up a repository definition for it. > This allows us to run an individual test bundle. > This is mostly useful to satisfy test dependencies - tests depend on RedDeer as a whole which is in the target platform. But most tests also have a RedDeer extension in the plugins directory: > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... > With that, let's move on to why it would be useful to have a stable repo for this, e.g. http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests/ > Imagine you want to run integration tests against the latest stable build. If you just checkout the integration tests and run a test plugin (using mvn verify), it will use everything from the latest nightly repos. > So to use latest stable release (jbt 4.4.1.Final / devstudio 10.1.0.GA), you need a couple of things: > 1. Checkout the corresponding branch of the integration tests - jbosstools-4.4.1.x in this case > 2. Make sure the proper devstudio is used to test against: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > -Ddevstudio.repository=https://devstudio.redhat.com/10.0/stable/updates > This also includes the TP, so RedDeer should be the correct version > 3. Make sure the proper integration-tests repo is used for dependencies > Now this is what we currently don't have. Our root pom will set up the snapshots repo: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > So that's why I would like to have a stable repo of this which I could use. > There is a workaround - run "mvn install" on the whole integration-tests repo before you run your test. This will install the correct version in your local repo and that may be then used by your test. But maven will probably still prefer the newer versions from the snapshots repo that is set up in the pom. > To give you an example what can break when you use the newest org.jboss.ide.eclipse.as.reddeer plugin, but run the EAP tests against devstudio 10.1.0.GA: > The EAP 7 server adapter had 7.0 in the type name in 10.1.0.GA, but in current master it's 7.x (to accommodate for the upcoming EAP 7.1). So if you want to test EAP 7.0.1 CP candidate build against devstudio 10.1.0.GA it will fail on this. > Sorry for the lengthy explanation, but I hope it's now clear why I'm requesting this. > Also, I'd be happy to hear if you have some suggestions how to do it differently. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23384) Include integration-tests (update site only) in staging and stable update sites

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23384?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-23384. -------------------------------- This issue will continue in JBIDE-23566, so closing this one. > Include integration-tests (update site only) in staging and stable update sites > ------------------------------------------------------------------------------- > > Key: JBIDE-23384 > URL: https://issues.jboss.org/browse/JBIDE-23384 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.2.Final > > > This will allow us the use case of running integration tests against the latest release of devstudio. This use case is required by EAP QE running our tests against their EAP development builds. > Currently we have this repo: > http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t... > We're referencing it from our root pom: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > And set up a repository definition for it. > This allows us to run an individual test bundle. > This is mostly useful to satisfy test dependencies - tests depend on RedDeer as a whole which is in the target platform. But most tests also have a RedDeer extension in the plugins directory: > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... > With that, let's move on to why it would be useful to have a stable repo for this, e.g. http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests/ > Imagine you want to run integration tests against the latest stable build. If you just checkout the integration tests and run a test plugin (using mvn verify), it will use everything from the latest nightly repos. > So to use latest stable release (jbt 4.4.1.Final / devstudio 10.1.0.GA), you need a couple of things: > 1. Checkout the corresponding branch of the integration tests - jbosstools-4.4.1.x in this case > 2. Make sure the proper devstudio is used to test against: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > -Ddevstudio.repository=https://devstudio.redhat.com/10.0/stable/updates > This also includes the TP, so RedDeer should be the correct version > 3. Make sure the proper integration-tests repo is used for dependencies > Now this is what we currently don't have. Our root pom will set up the snapshots repo: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > So that's why I would like to have a stable repo of this which I could use. > There is a workaround - run "mvn install" on the whole integration-tests repo before you run your test. This will install the correct version in your local repo and that may be then used by your test. But maven will probably still prefer the newer versions from the snapshots repo that is set up in the pom. > To give you an example what can break when you use the newest org.jboss.ide.eclipse.as.reddeer plugin, but run the EAP tests against devstudio 10.1.0.GA: > The EAP 7 server adapter had 7.0 in the type name in 10.1.0.GA, but in current master it's 7.x (to accommodate for the upcoming EAP 7.1). So if you want to test EAP 7.0.1 CP candidate build against devstudio 10.1.0.GA it will fail on this. > Sorry for the lengthy explanation, but I hope it's now clear why I'm requesting this. > Also, I'd be happy to hear if you have some suggestions how to do it differently. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4125) Provide environment variable to override developers.redhat.com in download manager URLs

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-4125?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-4125: ------------------------------------- I was given the access to the developers.stage.redhat.com and tested downloading and installation of CDK RC1(+ vagrantbox) and jbds (devstudio-10.2.0.AM3-v20161104-1659-B6372-installer-standalone.jar) from stage server via locally built platform installer. Everything seems fine, I am closing this issue. Just little summary, what was required to successfully go through installation process: Set up DM_STAGE_HOST to proper staging address (developers.stage.redhat.com), next, set up DSI_REJECT_UNAUTHORIZED to false, to gain access to stage server download page, change dmUrl values to staging url of tested components in requirements files and also adjusting shasums of these components. > Provide environment variable to override developers.redhat.com in download manager URLs > --------------------------------------------------------------------------------------- > > Key: JBDS-4125 > URL: https://issues.jboss.org/browse/JBDS-4125 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.2.0.GA > > Attachments: install.log > > > This is required to support testing online installer with staged download manager -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4070) DevStudio / external OpenShift fails deployment

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-4070?page=com.atlassian.jira.plugin.... ] Marián Labuda commented on JBDS-4070: ------------------------------------- If it is really just different deployment path, in the OpenShift Server Adapter wizard on the wizard page with selection of an eclipse project and OpenShift service, there is Advance section in the bottom of the page. After unfolding the section, there is a checkbox to change pod deployment path (by default is used the inferred one). Uncheck checkbox and change deployment path. Could work. > DevStudio / external OpenShift fails deployment > ----------------------------------------------- > > Key: JBDS-4070 > URL: https://issues.jboss.org/browse/JBDS-4070 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift > Affects Versions: 10.1.0.GA > Environment: DevStudio as used with an external OpenShift > Reporter: Rick Wagner > Assignee: Jeff MAURY > Labels: openshift_v3 > Fix For: 10.2.0.GA > > Attachments: OSDeployRecreate.docx, eap-app-server-adapter-publish.png, eap-app-server-adapter-settings.png, kitchensink-ear-deployed-succcessfully.png, kitchensink-ear-projects.png, new-openshift-server-adapter.png > > > If DevStudio (with Server Adapter configured for external OpenShift) is used to deploy an application developed in DevStudio, errors result. > The reporting user shows indications additional 'deploy' directories are being synthesized as the binary target location. The log reports: > 15:59:41,588 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0010: Scan found incompletely copied file content for deployment /opt/eap/standalone/deployments/deploy/deploy/deploy/deploy/deploy/deploy/activemq-rar.rar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23300) OpenShift connection created by CDK server adapter does not store password in secure storage

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23300?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23300. --------------------------------- I verified this with devstudio-10.2.0.GA-v20161125-1418-B55-installer-standalone.jar and CDK 2.3.0.rc2. And it works as expected - after I start cdk, the connection to openshift is established and the password is added to secure storage. Closing. > OpenShift connection created by CDK server adapter does not store password in secure storage > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23300 > URL: https://issues.jboss.org/browse/JBIDE-23300 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Labels: connection > Fix For: 4.4.2.AM3 > > > OpenShift 3 connection created by a CDK server adapter does not successfully store password in secure storage although a checkbox in the Connection dialog is checked. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4168) Updated the "Setting up CDK software components" for adding Vagrant box

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4168?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-4168. ------------------------------- > Updated the "Setting up CDK software components" for adding Vagrant box > ----------------------------------------------------------------------- > > Key: JBDS-4168 > URL: https://issues.jboss.org/browse/JBDS-4168 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: cdk, documentation > Reporter: Budh Ram Gurung > Fix For: 10.2.0.AM3 > > > We have updated our Vagrantfiles so that user can use any customized box name. > This can be easily done with adding an environment variable like *BOX*. > The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4174) Install Vagrant and Virtualbox for macOS out of Apple DIsk Image

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4174?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4174. ----------------------------- Ran the latest installer -> downloaded both files -> got asked twice for privileges -> installed both successfully. I think it works :) > Install Vagrant and Virtualbox for macOS out of Apple DIsk Image > ---------------------------------------------------------------- > > Key: JBDS-4174 > URL: https://issues.jboss.org/browse/JBDS-4174 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM3 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.2.0.GA > > > Installation can be done in two commands: > 1. mounting dmg file as a folder > 2. running macOS installer with pkg file name for corresponding application > To trigger privilege lifting both commands should be wrapped with osascript command that require administartive account. > Consequences are there are going o be two requests for administrator credentials. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4178) Environment variable with password is not passed to DevStudio started form installer on macOS

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4178?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4178. ----------------------------- Confirming CDK starts without prompting for password after installation. > Environment variable with password is not passed to DevStudio started form installer on macOS > --------------------------------------------------------------------------------------------- > > Key: JBDS-4178 > URL: https://issues.jboss.org/browse/JBDS-4178 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM3 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.2.0.GA > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4187) oc client tool is not added to PATH after installation on macOS

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4187?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4187. ----------------------------- Verified, oc is now available on path. > oc client tool is not added to PATH after installation on macOS > --------------------------------------------------------------- > > Key: JBDS-4187 > URL: https://issues.jboss.org/browse/JBDS-4187 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.GA > Environment: macOS > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.2.0.GA > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4186) oc client tool has no execution permission after install on macOS

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4186?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4186. ----------------------------- Confirming OC file now has -rwxr-xr-x permissions. Closing. > oc client tool has no execution permission after install on macOS > ----------------------------------------------------------------- > > Key: JBDS-4186 > URL: https://issues.jboss.org/browse/JBDS-4186 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.2.0.GA > > > After installation on macOS devstudio cannot get pod logs, because it cannot execute oc from cdk/bin folder. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2016