[JBoss JIRA] (JBIDE-24899) Deploy Docker Image wizard: Image not found
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-24899?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-24899:
-------------------------------------
Story Points: 13
> Deploy Docker Image wizard: Image not found
> -------------------------------------------
>
> Key: JBIDE-24899
> URL: https://issues.jboss.org/browse/JBIDE-24899
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker, openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Major
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.13.0.AM1
>
> Attachments: image-2017-08-29-09-50-20-927.png
>
>
> Exception in Error log:
> {code:java}
> Failed to inspect image: '172.30.1.1:5000/test/hola:latest'
> com.spotify.docker.client.exceptions.ImageNotFoundException: Image not found: 172.30.1.1:5000/test/hola:latest
> at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1330)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImageInfo(DockerConnection.java:896)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.lookupImageMetadata(DeployImageWizardModel.java:655)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:354)
> 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)
> Caused by: com.spotify.docker.client.exceptions.DockerRequestException: Request error: GET https://192.168.42.121:2376/images/172.30.1.1:5000/test/hola:latest/json: 404
> at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084)
> at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2023)
> at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1326)
> ... 5 more
> Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found
> at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1008)
> at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:816)
> at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:92)
> at org.glassfish.jersey.client.JerseyInvocation$5.completed(JerseyInvocation.java:773)
> at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:198)
> at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:79)
> at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:180)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
> at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:340)
> at org.glassfish.jersey.client.ClientRuntime$3.run(ClientRuntime.java:210)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> eclipse.buildId=11.1.0.AM1-v20170824-1835-B873
> java.version=1.8.0_141
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26694) Server adapter: should be able to freely set a war name
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26694?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26694:
-------------------------------------
Story Points: 34
> Server adapter: should be able to freely set a war name
> -------------------------------------------------------
>
> Key: JBIDE-26694
> URL: https://issues.jboss.org/browse/JBIDE-26694
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.12.0.AM1
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Labels: server_adapter
> Fix For: 4.13.0.AM1
>
> Attachments: console-output-1.png, console-output-2.png, server-adapter-configuration.png, switch-location.png
>
>
> For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it.
> Steps:
> # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image
> # ASSERT: *websocket-chat* application is imported into your workspace
> # ASSERT: server adapter *jboss-webserver31-tomcat* is created
> # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running)
> # EXEC: start the server adapter
> # ASSERT: RSync is executed and the output is visible in the "Console"
> Result:
> If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar*
> !console-output-1.png!
> Expected result:
> I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*).
> Currently, to achieve this I have to do the following:
> # EXEC: create the following xml snippet (notice the *outputName* property for the module)
> and make sure it reads as follows:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <deployment>
> <local>
> <module id="org.eclipse.jst.jee.server:websocket-chat">
> <property key="tempLocation" value="" />
> <property key="location" value="" />
> <property key="outputName" value="ROOT" />
> </module>
> </local>
> </deployment>
> {code}
> # EXEC: html-encode, join it into a single line and copy it (into the clipboard)
> # EXEC: open the properties for the server adapter and hit "Switch Location"
> !switch-location.png!
> # ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter.
> !server-adapter-configuration.png!
> # EXEC: open the file with the *XML Editor*
> # EXEC: in your *XML Editor*: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="*
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>">
> <list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/>
> </server>
> {code}
> # EXEC: Save the editor and restart the server
> Result:
> Syncing now happens into a folder *ROOT*
> !console-output-2.png!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-24498) Deploy Docker Image wizard: results dialog is not very informative
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-24498?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-24498:
-------------------------------------
Story Points: 8
> Deploy Docker Image wizard: results dialog is not very informative
> ------------------------------------------------------------------
>
> Key: JBIDE-24498
> URL: https://issues.jboss.org/browse/JBIDE-24498
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.13.0.AM1
>
> Attachments: image-2017-05-23-11-07-21-461.png
>
>
> steps to reproduce:
> # ASSERT: have a docker connection
> # ASSERT: have an OpenShift connection
> # EXEC: in "Docker Explorer": select an image and pick "Deploy to OpenShift..."
> # ASSERT: deploy docker image wizard pops up
> # EXEC: provide settings and finish the wizard
> Result:
> A dialog pops up informing you about the result of your deployment.
> !image-2017-05-23-11-07-21-461.png!
> But the dialog is not very informative, it's far from obvious what the different informations are all about:
> * If there's an error deploying (ex. you have chosen to "Push to the registry" but the registry is not reachable from the local docker daemon that holds the image that you want to deploy) the error is displayed in the title area. It's not visible at first sight that it's an error. Only by reading you're discovering it. (ex. add an error decorator)
> * There's a list of items. Nothing in the dialog tells the user what these items are.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-24899) Deploy Docker Image wizard: Image not found
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-24899?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-24899:
-------------------------------------
Sprint: devex #169 July 2019
> Deploy Docker Image wizard: Image not found
> -------------------------------------------
>
> Key: JBIDE-24899
> URL: https://issues.jboss.org/browse/JBIDE-24899
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker, openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Major
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.13.0.AM1
>
> Attachments: image-2017-08-29-09-50-20-927.png
>
>
> Exception in Error log:
> {code:java}
> Failed to inspect image: '172.30.1.1:5000/test/hola:latest'
> com.spotify.docker.client.exceptions.ImageNotFoundException: Image not found: 172.30.1.1:5000/test/hola:latest
> at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1330)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImageInfo(DockerConnection.java:896)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.lookupImageMetadata(DeployImageWizardModel.java:655)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:354)
> 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)
> Caused by: com.spotify.docker.client.exceptions.DockerRequestException: Request error: GET https://192.168.42.121:2376/images/172.30.1.1:5000/test/hola:latest/json: 404
> at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084)
> at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2023)
> at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1326)
> ... 5 more
> Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found
> at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1008)
> at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:816)
> at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:92)
> at org.glassfish.jersey.client.JerseyInvocation$5.completed(JerseyInvocation.java:773)
> at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:198)
> at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:79)
> at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:180)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
> at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:340)
> at org.glassfish.jersey.client.ClientRuntime$3.run(ClientRuntime.java:210)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> eclipse.buildId=11.1.0.AM1-v20170824-1835-B873
> java.version=1.8.0_141
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26713) Installation of JBT 4.12.0.Final from Update Site Cannot Complete as Requested
by Koen Aers (Jira)
[ https://issues.jboss.org/browse/JBIDE-26713?page=com.atlassian.jira.plugi... ]
Koen Aers edited comment on JBIDE-26713 at 7/3/19 7:26 AM:
-----------------------------------------------------------
[~adietish] no problem at all...
[~jeffmaury] maybe it would also be good to get 'photon' out of the name of the urls in the email that gets sent out? i find it confusing... but maybe that should be part of another issue?
was (Author: koen.aers):
[~adietish]no problem at all...
[~jeffmaury]maybe it would also be good to get 'photon' out of the name of the urls in the email that gets sent out? i find it confusing... but maybe that should be part of another issue?
> Installation of JBT 4.12.0.Final from Update Site Cannot Complete as Requested
> ------------------------------------------------------------------------------
>
> Key: JBIDE-26713
> URL: https://issues.jboss.org/browse/JBIDE-26713
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 4.12.0.Final
> Reporter: Koen Aers
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.13.x
>
> Attachments: JBIDE-26568.mov
>
>
> While installing JBT from the update site at http://download.jboss.org/jbosstools/photon/staging/updates/core/4.12.0.F... in a fresh Eclipse JEE installation the installation does not finish as requested.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-24899) Deploy Docker Image wizard: Image not found
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-24899?page=com.atlassian.jira.plugi... ]
André Dietisheim reassigned JBIDE-24899:
----------------------------------------
Assignee: André Dietisheim
> Deploy Docker Image wizard: Image not found
> -------------------------------------------
>
> Key: JBIDE-24899
> URL: https://issues.jboss.org/browse/JBIDE-24899
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker, openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Major
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.13.0.AM1
>
> Attachments: image-2017-08-29-09-50-20-927.png
>
>
> Exception in Error log:
> {code:java}
> Failed to inspect image: '172.30.1.1:5000/test/hola:latest'
> com.spotify.docker.client.exceptions.ImageNotFoundException: Image not found: 172.30.1.1:5000/test/hola:latest
> at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1330)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImageInfo(DockerConnection.java:896)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.lookupImageMetadata(DeployImageWizardModel.java:655)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:354)
> 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)
> Caused by: com.spotify.docker.client.exceptions.DockerRequestException: Request error: GET https://192.168.42.121:2376/images/172.30.1.1:5000/test/hola:latest/json: 404
> at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084)
> at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2023)
> at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1326)
> ... 5 more
> Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found
> at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1008)
> at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:816)
> at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:92)
> at org.glassfish.jersey.client.JerseyInvocation$5.completed(JerseyInvocation.java:773)
> at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:198)
> at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:79)
> at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:180)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
> at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:340)
> at org.glassfish.jersey.client.ClientRuntime$3.run(ClientRuntime.java:210)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> eclipse.buildId=11.1.0.AM1-v20170824-1835-B873
> java.version=1.8.0_141
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26694) Server adapter: should be able to freely set a war name
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26694?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26694:
-------------------------------------
Sprint: devex #169 July 2019
> Server adapter: should be able to freely set a war name
> -------------------------------------------------------
>
> Key: JBIDE-26694
> URL: https://issues.jboss.org/browse/JBIDE-26694
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.12.0.AM1
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Labels: server_adapter
> Fix For: 4.13.0.AM1
>
> Attachments: console-output-1.png, console-output-2.png, server-adapter-configuration.png, switch-location.png
>
>
> For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it.
> Steps:
> # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image
> # ASSERT: *websocket-chat* application is imported into your workspace
> # ASSERT: server adapter *jboss-webserver31-tomcat* is created
> # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running)
> # EXEC: start the server adapter
> # ASSERT: RSync is executed and the output is visible in the "Console"
> Result:
> If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar*
> !console-output-1.png!
> Expected result:
> I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*).
> Currently, to achieve this I have to do the following:
> # EXEC: create the following xml snippet (notice the *outputName* property for the module)
> and make sure it reads as follows:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <deployment>
> <local>
> <module id="org.eclipse.jst.jee.server:websocket-chat">
> <property key="tempLocation" value="" />
> <property key="location" value="" />
> <property key="outputName" value="ROOT" />
> </module>
> </local>
> </deployment>
> {code}
> # EXEC: html-encode, join it into a single line and copy it (into the clipboard)
> # EXEC: open the properties for the server adapter and hit "Switch Location"
> !switch-location.png!
> # ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter.
> !server-adapter-configuration.png!
> # EXEC: open the file with the *XML Editor*
> # EXEC: in your *XML Editor*: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="*
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>">
> <list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/>
> </server>
> {code}
> # EXEC: Save the editor and restart the server
> Result:
> Syncing now happens into a folder *ROOT*
> !console-output-2.png!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-24498) Deploy Docker Image wizard: results dialog is not very informative
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-24498?page=com.atlassian.jira.plugi... ]
André Dietisheim reassigned JBIDE-24498:
----------------------------------------
Assignee: André Dietisheim
> Deploy Docker Image wizard: results dialog is not very informative
> ------------------------------------------------------------------
>
> Key: JBIDE-24498
> URL: https://issues.jboss.org/browse/JBIDE-24498
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.13.0.AM1
>
> Attachments: image-2017-05-23-11-07-21-461.png
>
>
> steps to reproduce:
> # ASSERT: have a docker connection
> # ASSERT: have an OpenShift connection
> # EXEC: in "Docker Explorer": select an image and pick "Deploy to OpenShift..."
> # ASSERT: deploy docker image wizard pops up
> # EXEC: provide settings and finish the wizard
> Result:
> A dialog pops up informing you about the result of your deployment.
> !image-2017-05-23-11-07-21-461.png!
> But the dialog is not very informative, it's far from obvious what the different informations are all about:
> * If there's an error deploying (ex. you have chosen to "Push to the registry" but the registry is not reachable from the local docker daemon that holds the image that you want to deploy) the error is displayed in the title area. It's not visible at first sight that it's an error. Only by reading you're discovering it. (ex. add an error decorator)
> * There's a list of items. Nothing in the dialog tells the user what these items are.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-24498) Deploy Docker Image wizard: results dialog is not very informative
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-24498?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-24498:
-------------------------------------
Sprint: devex #169 July 2019
> Deploy Docker Image wizard: results dialog is not very informative
> ------------------------------------------------------------------
>
> Key: JBIDE-24498
> URL: https://issues.jboss.org/browse/JBIDE-24498
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.13.0.AM1
>
> Attachments: image-2017-05-23-11-07-21-461.png
>
>
> steps to reproduce:
> # ASSERT: have a docker connection
> # ASSERT: have an OpenShift connection
> # EXEC: in "Docker Explorer": select an image and pick "Deploy to OpenShift..."
> # ASSERT: deploy docker image wizard pops up
> # EXEC: provide settings and finish the wizard
> Result:
> A dialog pops up informing you about the result of your deployment.
> !image-2017-05-23-11-07-21-461.png!
> But the dialog is not very informative, it's far from obvious what the different informations are all about:
> * If there's an error deploying (ex. you have chosen to "Push to the registry" but the registry is not reachable from the local docker daemon that holds the image that you want to deploy) the error is displayed in the title area. It's not visible at first sight that it's an error. Only by reading you're discovering it. (ex. add an error decorator)
> * There's a list of items. Nothing in the dialog tells the user what these items are.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months