September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24882) Can't rebuild releng image

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24882?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-24882: --------------------------------- Git Pull Request: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/m..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/c... (was: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/m...) > Can't rebuild releng image > -------------------------- > > Key: JBIDE-24882 > URL: https://issues.jboss.org/browse/JBIDE-24882 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM2 > > > It is not possible to rebuild "rhel7-x64-jbds-releng" image because update image pipeline \[1\] fails during cloning of mwqa-env-suite repository \[2\] > \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Central... > \[2\] https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-env-suite > {code} > MW QA environment configured > + echo 'MW QA environment configured' > + test_repo=git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git > + test='git clone git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git && ./mwqa-env-suite/run.sh jbds docker releng' > + ssh -o PasswordAuthentication=no -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o Loglevel=error -i /tmp/os.key.QYcvv9Sg hudson(a)10.8.242.82 'git clone git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git && ./mwqa-env-suite/run.sh jbds docker releng' > Cloning into 'mwqa-env-suite'... > Bad owner or permissions on /home/hudson/.ssh/config > fatal: Could not read from remote repository. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24889) Installer tests doesn't work on x86 servers.

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24889?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-24889. -------------------------------- PR has been merged, closing. > Installer tests doesn't work on x86 servers. > -------------------------------------------- > > Key: JBIDE-24889 > URL: https://issues.jboss.org/browse/JBIDE-24889 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: install-tests > Affects Versions: 4.5.1.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM2 > > > Installer tests \[1\], \[2\] are failing on x86 slaves. It seems that env variable NATIVE_TOOLS was't set. > {code} > [fedora26-x86] $ /qa/tools/opt/groovy-2.4.3/bin/groovy -DuseWhiteSpace /mnt/hudson_workspace/workspace/Devstudio_Installation/Devstudio_installation/devstudio_installation_standalone_11.matrix/jdk/jdk1.8/label/fedora26-x86/devstudio-installer.test/src/main/groovy/prepareJBDSInstall.groovy https://devstudio.redhat.com/11/snapshots/builds/devstudio.product_master... /mnt/hudson_workspace/workspace/Devstudio_Installation/Devstudio_installation/devstudio_installation_standalone_11.matrix/jdk/jdk1.8/label/fedora26-x86 > groovy: JAVA_HOME is not defined correctly, can not execute: ${NATIVE_TOOLS}/jdk1.8.0_last/bin/java > {code} > \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/user/lvalach... > \[2\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/user/lvalach... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24975) cdk3.devstudio.it.weekly and smoke tests fail on most OS combos

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24975?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-24975: --------------------------------------- This topic (having CDK running on all platform) is a bit more complicated, though, this is definitely final aim (to have it run on full matrix). First of all, integration tests were quite slow (which can be expected as one must start/stop cdk server adapter to test something), and thus, https://issues.jboss.org/browse/JBIDE-24656 was created and finally closed. This should results in two suite, one smoke suite that is usually under 20 minutes (tests itself, downloading plugins for devstudio and starting through maven takes another 20-30 minutes) and all tests suite, that takes more time and can be run less frequently. I plan to use smoke suite to be triggered by successful cdk-build and to verify nothing was broken in tooling by changes in cdk api (https://issues.jboss.org/browse/CDK-165). Secondly, to be able to run cdk in devstudio some steps must be taken beforehand. for this purpose I have created some script that would ease the pain of cross-platform automation for linux (shell is used) and windows platform (here we operate with cygwin), so far. I did not have tested MacOS yet. (https://github.com/odockal/cdk-scripts). Another thing was migrating to openstack 10 which could resolve some mostly virtualization issues as CDK needs to run on machine with nested virtualization enabled. But also another problems appeared like win 10 images have virtualization switched off (https://issues.jboss.org/browse/JBIDE-24838) or until-now always working virtualization on rhel7 and win7vbox slaves (https://redhat.service-now.com/surl.do?n=PNT0052470). So I would suggest to keep the os matrix narrowed to rhel7 label. In day or two I plan to add win7vbox label (this is windows 7 image with virtualization allowed and with installed virtualbox. Which could be stable matrix for now, except above mentioned issue with virtualization. Adding Mac is next step after adding windows platform. WDYT [~nickboldt] ? > cdk3.devstudio.it.weekly and smoke tests fail on most OS combos > --------------------------------------------------------------- > > Key: JBIDE-24975 > URL: https://issues.jboss.org/browse/JBIDE-24975 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, integration-tests > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Ondrej Dockal > Attachments: cdk3.devstudio.it.smoke.png, cdk3.devstudio.it.weekly.png > > > cdk3.devstudio.it.weekly and smoke tests are failing pretty much everywhere. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > !cdk3.devstudio.it.weekly.png|thumbnail! > !cdk3.devstudio.it.smoke.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24982) Include project name in created server adapter

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24982?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24982: ---------------------------------- Labels: openhift_v3 server_adapter (was: ) > Include project name in created server adapter > ---------------------------------------------- > > Key: JBIDE-24982 > URL: https://issues.jboss.org/browse/JBIDE-24982 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Josef Kopriva > Labels: openhift_v3, server_adapter > Attachments: image-2017-09-05-12-39-41-409.png > > > Please add project name in newly created server adapter for openshift application, so user can distinguish between same application in different projects. > !image-2017-09-05-12-39-41-409.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24982) Include project name in created server adapter

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-24982: ------------------------------------- Summary: Include project name in created server adapter Key: JBIDE-24982 URL: https://issues.jboss.org/browse/JBIDE-24982 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.5.1.AM2 Reporter: Josef Kopriva Attachments: image-2017-09-05-12-39-41-409.png Please add project name in newly created server adapter for openshift application, so user can distinguish between same application in different projects. !image-2017-09-05-12-39-41-409.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4537) Ensure Datatools and WTP-JPT (Dali) are available in DevTools (rh-eclipse47) so downstream rh-eclipse47-devstudio can use it

by Mat Booth (JIRA)

[ https://issues.jboss.org/browse/JBDS-4537?page=com.atlassian.jira.plugin.... ] Mat Booth commented on JBDS-4537: --------------------------------- It's a sub-package of eclipse-webtools: $ dnf install eclipse-webtools-dali > Ensure Datatools and WTP-JPT (Dali) are available in DevTools (rh-eclipse47) so downstream rh-eclipse47-devstudio can use it > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4537 > URL: https://issues.jboss.org/browse/JBDS-4537 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: rpm, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > > Mat says that Eclipse DTP and WTP-JPT are already in Fedora. > So we need to ensure Datatools and WTP-JPT (Dali) are ALSO available in DevTools (rh-eclipse47); then downstream rh-eclipse47-devstudio can use it -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24802) Connection wizard: Lots of unnecessary errors in Error Log when filling oc location, Finish enabled even if oc location empty

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24802?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-24802. --------------------------------- Closing - works as expected and finish button is not enabled if oc location is empty. Verified in: Red Hat JBoss Developer Studio Version: 11.1.0.AM2 Build id: AM2-v20170905-0703-B967 Build date: 20170905-0703 > Connection wizard: Lots of unnecessary errors in Error Log when filling oc location, Finish enabled even if oc location empty > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24802 > URL: https://issues.jboss.org/browse/JBIDE-24802 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.1.AM2 > > Attachments: Spectacle.F10835.png > > > On-the-fly validation of "oc location" field in ConnectionWizardPage puts lot of errors into error log. I think that the on the fly validation should not be so agressive. > !Spectacle.F10835.png! > And another thing: Is there any reason why Finish is enabled even when there is not valid value in oc location field? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21372) Server Adapter: automatically create a server for new apps

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21372?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-21372. --------------------------------- Closing - works as expected. Verified in: Red Hat JBoss Developer Studio Version: 11.1.0.AM2 Build id: AM2-v20170905-0703-B967 Build date: 20170905-0703 > Server Adapter: automatically create a server for new apps > ---------------------------------------------------------- > > Key: JBIDE-21372 > URL: https://issues.jboss.org/browse/JBIDE-21372 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM1 > > > Currently one has to create the OpenShift 3 server adapter manually by using the menu File > New > Server > OpenShift 3 (or context menu in the Server view). We should now also create the server adapter when one successfully finishes the new/import application wizard. To achieve this we'll have to include a page in the new/import-application wizard for the required server settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24146) Support pipeline deployment style

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24146?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24146: ------------------------------------------ There's a nice example on github showing pipeline deployment: https://github.com/siamaksade/openshift-cd-demo > Support pipeline deployment style > --------------------------------- > > Key: JBIDE-24146 > URL: https://issues.jboss.org/browse/JBIDE-24146 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: application_wizard, openshift, openshift_v3 > Fix For: 4.5.x > > Attachments: jenkins-pipeline-template.png, jenkins-variants.png, pipeline-build.png, webui-edit-pipeline-file.png > > > In the web-console jenkins pipelines are supported in the following way: > * when opening up an empty project you get a special template: > !jenkins-pipeline-template.png! > * which offers 2 different jenkins variants (and a full example that contains app source and build pipeline): > !jenkins-variants.png! > * once executed you get a special build type *pipeline* > !pipeline-build.png! > * the full example template is using the following build config with the strategy type *JenkinsPipeline*: > {code} > apiVersion: v1 > kind: BuildConfig > metadata: > name: sample-pipeline > namespace: gulu > selfLink: /oapi/v1/namespaces/gulu/buildconfigs/sample-pipeline > uid: 12dec3c8-1948-11e7-a217-0251082287a6 > resourceVersion: '3757' > creationTimestamp: '2017-04-04T15:05:00Z' > labels: > app: jenkins-pipeline-example > name: sample-pipeline > template: application-template-sample-pipeline > annotations: > pipeline.alpha.openshift.io/uses: >- > [{"name": "nodejs-mongodb-example", "namespace": "", "kind": > "DeploymentConfig"}] > spec: > triggers: > - type: GitHub > github: > secret: secret101 > - type: Generic > generic: > secret: secret101 > runPolicy: Serial > source: > type: None > strategy: > type: JenkinsPipeline > jenkinsPipelineStrategy: > jenkinsfile: >- > node('nodejs') { > stage 'build' > openshiftBuild(buildConfig: 'nodejs-mongodb-example', showBuildLogs: > 'true') > stage 'deploy' > openshiftDeploy(deploymentConfig: 'nodejs-mongodb-example') > } > output: {} > resources: {} > postCommit: {} > nodeSelector: null > status: > lastVersion: 1 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24981) Server adapter: fails to start if app has no dc but only a rc

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24981?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24981: ------------------------------- Issue Type: Bug (was: Enhancement) > Server adapter: fails to start if app has no dc but only a rc > ------------------------------------------------------------- > > Key: JBIDE-24981 > URL: https://issues.jboss.org/browse/JBIDE-24981 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openhift_v3, server_adapter > Fix For: 4.5.x > > Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-22-15-46-383.png, image-2017-09-04-22-17-26-655.png, started-even-though-failed-starting.png > > > # ASSERT: make sure that you have an app that has NO deployment config, just a replication controller > (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json]) > # EXEC: in explorer: once your app is created, create a server adapter for it, binding the imported source to the replication controller that's available > # ASSERT: the server adapter is starting up > !image-2017-09-04-22-15-46-383.png! > Result: > The server adapter keeps starting up without reaching "[Started]", waiting at 7%. Finally - > after a few minutes, it fails with the following error: > !image-2017-09-04-22-17-26-655.png! > > Furthermore, once you close the error dialog the server is in state "[Started]" even though it errored while starting up > !started-even-though-failed-starting.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 September 2017