August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22597) Deploy Docker wizard: Deploy docker image to openshift may finish without user being notified

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22597?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22597: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.1.Final) > Deploy Docker wizard: Deploy docker image to openshift may finish without user being notified > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22597 > URL: https://issues.jboss.org/browse/JBIDE-22597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.x > > > When a Docker image is deployed to Openshift and this is an update (Openshift resources already exist), then image is pushed to the registry but no feedback is returned to the user. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22304) Server Editor: Pod deployment path is not shown

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22304?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22304: ------------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Server Editor: Pod deployment path is not shown > ----------------------------------------------- > > Key: JBIDE-22304 > URL: https://issues.jboss.org/browse/JBIDE-22304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_editor > Fix For: 4.4.2.AM1 > > > In Server Adapter wizard is not shown Pod deployment path. Widget supposed to display the path is empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22243) Properties: "Refresh" has no effect

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22243: ------------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Properties: "Refresh" has no effect > ----------------------------------- > > Key: JBIDE-22243 > URL: https://issues.jboss.org/browse/JBIDE-22243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Fix For: 4.4.2.AM1 > > Attachments: refreshing-wont-help.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22239: ------------------------------------------ [~jcantrill] can you please comment? I'm unsure. > Allow a user to choose to permanently update their desired replicas for their deployment > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22239 > URL: https://issues.jboss.org/browse/JBIDE-22239 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Viacheslav Kabanovich > Labels: openshift_v3 > Fix For: 4.4.1.Final > > > When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest: > * Adding a custom dialog in the "..to.." option > * Update to use a spinner > * Add a checkbox to 'make the change perminent' > * If checkbox=true, you should only need to update the dc if it has a configchange trigger. > * Optionally show checkbox if unable to determine the dc associated with the deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21857: ------------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.2.AM1 > > Attachments: HCRFailure.zip > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22804) Application wizard: Git reference is ignored for application templates

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22804?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22804: ------------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Application wizard: Git reference is ignored for application templates > ---------------------------------------------------------------------- > > Key: JBIDE-22804 > URL: https://issues.jboss.org/browse/JBIDE-22804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.4.2.AM1 > > > When creating a new OpenShift 3 application based on application template (e.g. eap64) and I change value of Git ref, the new value is ignored and still the old one is used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22804) Application wizard: Git reference is ignored for application templates

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22804?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22804: ------------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.2.AM1) > Application wizard: Git reference is ignored for application templates > ---------------------------------------------------------------------- > > Key: JBIDE-22804 > URL: https://issues.jboss.org/browse/JBIDE-22804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.4.1.Final > > > When creating a new OpenShift 3 application based on application template (e.g. eap64) and I change value of Git ref, the new value is ignored and still the old one is used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22804) Application wizard: Git reference is ignored for application templates

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22804?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22804: ------------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Application wizard: Git reference is ignored for application templates > ---------------------------------------------------------------------- > > Key: JBIDE-22804 > URL: https://issues.jboss.org/browse/JBIDE-22804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.4.1.Final > > > When creating a new OpenShift 3 application based on application template (e.g. eap64) and I change value of Git ref, the new value is ignored and still the old one is used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22767) Deploy Docker Wizard: Create image stream contains wrong tags in some cases

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22767?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22767: ------------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Deploy Docker Wizard: Create image stream contains wrong tags in some cases > --------------------------------------------------------------------------- > > Key: JBIDE-22767 > URL: https://issues.jboss.org/browse/JBIDE-22767 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > Fix For: 4.4.2.AM1 > > > In Deploy Image to OpenShift wizard when I am trying to deploy image docker.io/openshift/hello-openshift:v1.2.1, the image stream created contains some weird tags. If I deploy this image via oc binary then a created image stream contains correct tag v1.2.1, but from tooling it contains more tags and none of them is the desired one (there are 0.4, 0.5, latest...). > Some behaviour is also common for normal usage. When deploying a image with tag latest, there are also defined other tags. OC binary creates IS only with the one tag, the one which was passed as "partial" argument when deploying an image. > Consequences of this issue are no pods created once the deploy image to OpenShift is finished. User has to manually trigger Deploy Latest from context menu of a deployment configuration to spin up an application pod. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.1.Final) > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.x > > Original Estimate: 2 days > Time Spent: 3 days > Remaining Estimate: 3 days > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 August 2016