August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24501) Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24501?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24501: ------------------------------------- Attachment: screenshot-1.png > Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24501 > URL: https://issues.jboss.org/browse/JBIDE-24501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: image-2017-05-23-12-00-51-733.png, image-2017-05-23-12-07-14-028.png, image-2017-05-23-12-10-06-694.png, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24501) Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24501?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24501: ------------------------------------- Steps to Reproduce: # ASSERT: have the CDK with the registry that's not publicly reachable # ASSERT: have a project with a docker file in your workspace (ex. clone git@github.com:redhat-helloworld-msa/hola.git) # ASSERT: have a connection to the docker daemon in the CDK3 # EXEC: in package explorer: select your Dockerfile and pick Run As > Docker Image Build. Provide some image name and version, pick *Docker Connection* to the docker daemon in the CDK # EXEC: once the image is built, go to "Docker Explorer", select the Docker image that you built and select "Deploy to OpenShift..." # EXEC: In deploy docker image wizard: check "Push Image to Registry" and finish the wizard # ASSERT: once the push is finished, the freshly pushed image should show up in the Docker explorer !image-2017-05-23-12-00-51-733.png! # EXEC: in "Docker Explorer": select this image and pick "Deploy to OpenShift..." # ASSERT: "Deploy Docker Image" wizard shows up, having "Image Name" set to your Docker image with the docker registry prefix !image-2017-05-23-12-07-14-028.png! # EXEC: hit "Next" Result: The image name lookup fails, and 2 error dialogs show up: One that tells you that the lookup failed and one that tells you about an NPE that happened: !image-2017-05-23-12-10-06-694.png! !screenshot-1.png! In the Eclipse log you'll find the following: {code} java.lang.NullPointerException at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DockerConfigMetaData.env(DockerConfigMetaData.java:69) at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:356) at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) {code} was: # ASSERT: have the CDK with the registry that's not publicly reachable # ASSERT: have a project with a docker file in your workspace (ex. clone git@github.com:redhat-helloworld-msa/hola.git) # ASSERT: have a connection to the docker daemon in the CDK3 # EXEC: in package explorer: select your Dockerfile and pick Run As > Docker Image Build. Provide some image name and version, pick *Docker Connection* to the docker daemon in the CDK # EXEC: once the image is built, go to "Docker Explorer", select the Docker image that you built and select "Deploy to OpenShift..." # EXEC: In deploy docker image wizard: check "Push Image to Registry" and finish the wizard # ASSERT: once the push is finished, the freshly pushed image should show up in the Docker explorer !image-2017-05-23-12-00-51-733.png! # EXEC: in "Docker Explorer": select this image and pick "Deploy to OpenShift..." # ASSERT: "Deploy Docker Image" wizard shows up, having "Image Name" set to your Docker image with the docker registry prefix !image-2017-05-23-12-07-14-028.png! # EXEC: hit "Next" Result: The image name lookup fails, and 2 error dialogs show up: One that tells you that the lookup failed and one that tells you about an NPE that happened: !image-2017-05-23-12-10-06-694.png! In the Eclipse log you'll find the following: {code} java.lang.NullPointerException at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DockerConfigMetaData.env(DockerConfigMetaData.java:69) at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:356) at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) {code} > Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24501 > URL: https://issues.jboss.org/browse/JBIDE-24501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: image-2017-05-23-12-00-51-733.png, image-2017-05-23-12-07-14-028.png, image-2017-05-23-12-10-06-694.png, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24780) Creatinng an OpenShift server adapter should suggest placing Web facet on related project(s)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24780?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-24780: ---------------------------------------- It's the case of a C# ASP.NET application created with aCute. The application isn't created with the Web facet simply because the C# tools don't depend on WTP. However, when trying to bind it to OpenShift (and not really before), adding the Web facet seemed useful. Hence why I suggest to create the Facet as part of the "connect to OpenShift application" workflow. > Creatinng an OpenShift server adapter should suggest placing Web facet on related project(s) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24780 > URL: https://issues.jboss.org/browse/JBIDE-24780 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Mickael Istria > Fix For: 4.5.x > > > I've created an OpenShift Application from Eclipse IDE providing it an Eclipse Project as input. > Then I tried to create a server adapter for this project. It didn't work initially because the project isn't a Faceted Web project. I had to quit the OpenShift wizard, make the project a faceted one and restart the wizard. > I would expect the wizard to create a server adapter to suggest and link to a way to make the project associated with the application a web project in Eclipse IDE so it's one less step to understand for users before it works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4488) Very slow initial startup for Eclipse

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4488?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4488: ------------------------------------ I confirm that the restart after installation of some plugins takes long time (155s in my case). Clean rh-eclipse47-devstudio started in 90s. > Very slow initial startup for Eclipse > ------------------------------------- > > Key: JBDS-4488 > URL: https://issues.jboss.org/browse/JBDS-4488 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 11.0.0.AM2 > Environment: * rh-eclipse47 (http://download.eng.bos.redhat.com/rel-eng/DevTools-1.0-RHEL-7-Beta-1.0/c...) > * devstudio (https://devstudio.jboss.com/11/snapshots/builds/devstudio.rpm_master/2017...) > Reporter: Martin Coufal > Priority: Minor > > Launching Eclipse after installation of any plugins from Devstudio (Red Hat Central) takes VERY long time (around 180s). This is regression bug, for more details, see [1]. > Note: Also, launching rh-eclipse47 with Devstudio takes about 90s. > [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1392095 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24580) Remove integration tests of OpenShift 2 tooling

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24580?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24580. ------------------------------ Resolution: Done > Remove integration tests of OpenShift 2 tooling > ----------------------------------------------- > > Key: JBIDE-24580 > URL: https://issues.jboss.org/browse/JBIDE-24580 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.5.0.Final > > > Once OpenShift 2 tooling is removed from Tools/Devstudio, integration tests should be removed too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4488) Very slow initial startup for Eclipse

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4488?page=com.atlassian.jira.plugin.... ] Lukáš Valach reassigned JBDS-4488: ---------------------------------- Assignee: Nick Boldt > Very slow initial startup for Eclipse > ------------------------------------- > > Key: JBDS-4488 > URL: https://issues.jboss.org/browse/JBDS-4488 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 11.0.0.AM2 > Environment: * rh-eclipse47 (http://download.eng.bos.redhat.com/rel-eng/DevTools-1.0-RHEL-7-Beta-1.0/c...) > * devstudio (https://devstudio.jboss.com/11/snapshots/builds/devstudio.rpm_master/2017...) > Reporter: Martin Coufal > Assignee: Nick Boldt > Priority: Minor > > Launching Eclipse after installation of any plugins from Devstudio (Red Hat Central) takes VERY long time (around 180s). This is regression bug, for more details, see [1]. > Note: Also, launching rh-eclipse47 with Devstudio takes about 90s. > [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1392095 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24681) ITests: Get rid of AbstractCreateApplicationTest

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24681?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-24681: ------------------------------- Sprint: (was: devex #135 July 2017) > ITests: Get rid of AbstractCreateApplicationTest > ------------------------------------------------ > > Key: JBIDE-24681 > URL: https://issues.jboss.org/browse/JBIDE-24681 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.5.x > > > Use requirements instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24681) ITests: Get rid of AbstractCreateApplicationTest

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24681?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-24681: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > ITests: Get rid of AbstractCreateApplicationTest > ------------------------------------------------ > > Key: JBIDE-24681 > URL: https://issues.jboss.org/browse/JBIDE-24681 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.5.x > > > Use requirements instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24782) When creating an app, source resource path should be computed relatively to Git repo root

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24782?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24782: ------------------------------- Affects Version/s: 4.5.0.AM2 > When creating an app, source resource path should be computed relatively to Git repo root > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24782 > URL: https://issues.jboss.org/browse/JBIDE-24782 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Mickael Istria > Fix For: 4.5.x > > > When creating an OpenShift application with the OpenShift wizard and associating a Java project, I get asked for a source path. The default value is `app`. I would expect it, in case the project is under a Git repository, to automatically pre-set it to the relative path of the project in the Git repo, which is the most probable good value we can infer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24781) Propose to create OpenShift server adapters automatically when creating application

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24781?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24781: ------------------------------- Affects Version/s: 4.5.0.AM2 > Propose to create OpenShift server adapters automatically when creating application > ----------------------------------------------------------------------------------- > > Key: JBIDE-24781 > URL: https://issues.jboss.org/browse/JBIDE-24781 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Mickael Istria > Fix For: 4.5.1.AM1 > > > I'm trying to push an Eclipse project as an OpenShift application with Red Hat Developer Studio. When I create the application, the wizard asks me for an Eclipse project. I would expect that a server adapter would be created by default for this project, or that at least creating a server adapter would be proposed automatically (but remain cancellable). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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