June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21627) As a user I want to be able to expose services (create a route to an existing service)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21627?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21627: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > As a user I want to be able to expose services (create a route to an existing service) > --------------------------------------------------------------------------------------- > > Key: JBIDE-21627 > URL: https://issues.jboss.org/browse/JBIDE-21627 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.5.0.Final > > > It would be nice if we would have something similar as oc binary to expose an existing resource. To expose existing pods or services. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23711) Properites: "Edit default route" on Build config does nothing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23711?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23711: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Properites: "Edit default route" on Build config does nothing > ------------------------------------------------------------- > > Key: JBIDE-23711 > URL: https://issues.jboss.org/browse/JBIDE-23711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Labels: openshift_v3, properties > Fix For: 4.5.0.Final > > > Context menu of build configs in properties view has entry "Edit default route..." which does nothing. Is it even supposed to be there? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24442) Import wizard: does nothing if server is not reachable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24442?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24442: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Import wizard: does nothing if server is not reachable > ------------------------------------------------------ > > Key: JBIDE-24442 > URL: https://issues.jboss.org/browse/JBIDE-24442 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > 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 > 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 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24498) Deploy Docker Image wizard: results dialog is not very informative

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24498?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24498: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > 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: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.Final > > 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.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24177) Command to tune storage

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24177?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24177: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Command to tune storage > ----------------------- > > Key: JBIDE-24177 > URL: https://issues.jboss.org/browse/JBIDE-24177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24178) When deploying user should be able to tune autoscaling

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24178?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24178: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > When deploying user should be able to tune autoscaling > ------------------------------------------------------ > > Key: JBIDE-24178 > URL: https://issues.jboss.org/browse/JBIDE-24178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24179) Command to tune autoscaling

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24179?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24179: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Command to tune autoscaling > --------------------------- > > Key: JBIDE-24179 > URL: https://issues.jboss.org/browse/JBIDE-24179 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24185) Server adapter: approach to set nodejs/eap apps to debugging is inconsistent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24185?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24185: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Server adapter: approach to set nodejs/eap apps to debugging is inconsistent > ---------------------------------------------------------------------------- > > Key: JBIDE-24185 > URL: https://issues.jboss.org/browse/JBIDE-24185 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.Final > > > * eap > ** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*. > {code} > "com.redhat.dev-mode": "DEBUG:true", > {code} > ** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label > {code} > "com.redhat.dev-mode.port": "DEBUG_PORT:8787" > {code} > * nodejs > ** to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858* > {code} > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > {code} > The documentation actually confirms the fact that :5858 is the default: https://docs.openshift.org/latest/using_images/s2i_images/nodejs.html#nod... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23402) [WATCHER] Explorer: can "Deploy Latest" even if the build failed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23402: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > [WATCHER] Explorer: can "Deploy Latest" even if the build failed > ---------------------------------------------------------------- > > Key: JBIDE-23402 > URL: https://issues.jboss.org/browse/JBIDE-23402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Fix For: 4.5.0.Final > > Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png > > > When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete. > In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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