[JBoss JIRA] (JBIDE-26037) Deploy Docker Wizard: always prompts to create a new connection, does not preselect most recently used connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26037?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26037:
-------------------------------------
Issue Type: Enhancement (was: Bug)
> Deploy Docker Wizard: always prompts to create a new connection, does not preselect most recently used connection
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26037
> URL: https://issues.jboss.org/browse/JBIDE-26037
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Labels: deploy_docker_wizard
> Fix For: 4.6.x
>
> Attachments: image-2018-05-23-22-51-38-221.png
>
>
> steps:
> # ASSERT: make sure that you have at least 1 connection to a OpenShift server defined
> # ASSERT: do some operations involving your existing connection (ex. open children for it in OpenShift Explorer)
> # EXEC: in "Docker Explorer": select an image and pick in the context menu "Deploy to OpenShift..."
> Result:
> You get prompted to create a <New Connection>
> !image-2018-05-23-22-51-38-221.png!
> If you unfold the "Connection" combo box to list all connections you discover your connection and can pick it instead of the suggested <New Connection>
> Expected result:
> The connection page shows up with the most recently connection preselected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26043) Two paths to OC client in properties view for OpenShift connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26043?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-26043 at 5/29/18 9:20 AM:
-------------------------------------------------------------------
weird enough the double display isn't present for all connections:
* !screenshot-1.png!
* !screenshot-2.png!
* !screenshot-3.png!
was (Author: adietish):
weird enough the double display isn't present for all connections:
!screenshot-1.png!
!screenshot-2.png!
!screenshot-3.png!
> Two paths to OC client in properties view for OpenShift connection
> ------------------------------------------------------------------
>
> Key: JBIDE-26043
> URL: https://issues.jboss.org/browse/JBIDE-26043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Josef Kopriva
> Priority: Minor
> Labels: oc_binary, properties
> Fix For: 4.6.x
>
> Attachments: image-2018-05-28-14-48-08-877.png, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> !image-2018-05-28-14-48-08-877.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26043) Two paths to OC client in properties view for OpenShift connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26043?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-26043 at 5/29/18 9:20 AM:
-------------------------------------------------------------------
weird enough the double display isn't present for all connections:
!screenshot-1.png!
!screenshot-2.png!
!screenshot-3.png!
was (Author: adietish):
weird enough the double display isn't present for all connections:
* !screenshot-1.png!
* !screenshot-2.png!
* !screenshot-3.png!
> Two paths to OC client in properties view for OpenShift connection
> ------------------------------------------------------------------
>
> Key: JBIDE-26043
> URL: https://issues.jboss.org/browse/JBIDE-26043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Josef Kopriva
> Priority: Minor
> Labels: oc_binary, properties
> Fix For: 4.6.x
>
> Attachments: image-2018-05-28-14-48-08-877.png, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> !image-2018-05-28-14-48-08-877.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25905) [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25905?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25905:
------------------------------------------
fixed this while cleaning quite some code: [#1745|https://github.com/jbosstools/jbosstools-openshift/pull/1745]
> [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25905
> URL: https://issues.jboss.org/browse/JBIDE-25905
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.AM3
> Reporter: Denis Golovin
> Assignee: Andre Dietisheim
> Fix For: 4.6.0.AM3
>
> Attachments: service-ports.gif, services-routing-page-no-labels.png, services-routing-page.png
>
>
> [Service & Routing Settings] page in [Deploy Image to OpenShift] Wizard.
> Service Ports table starts to behave awkward after reset.
> steps:
> # ASSERT: have a docker image available that exposes several ports (ex. registry.access.redhat.com/openshift3/ose-haproxy-router:v3.7.14 which exposes 4 ports)
> # EXEC: in Docker Explorer: select your docker image and pick "Deploy to OpenShift..." from the context menu
> # ASSERT: "Deploy Image to OpenShift" wizard shows up
> # EXEC: get to the "Services & Routing Settings" page
> # ASSERT: all ports are listed, a port is checked in column "Used by route"
> !services-routing-page.png!
> # EXEC: hit "Reset" (and confirm the dialog that asks you if you want to reset the ports)
> # EXEC: click in the column "Used by route" on the 2nd port (or any unchecked entry)
> Result:
> Labels for columns "Name", "Service Port", "Pod Port" disappear
> !services-routing-page-no-labels.png!
> !service-ports.gif!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months