February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21703) Server adapter wizard: pod deployment path is always default (/opt/app-root/src)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21703?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21703: ------------------------------------- Steps to Reproduce: # ASSERT: make sure that you have an eap based app running # EXEC: launch server adapter wizard and pick OpenShift 3 server adapter. Pick your connection and get to the next page. # ASSERT: New Server dialog shows up # EXEC: inspect the Pod Deployment Path Result: The wizard report "/opt/app-root/src" Expected result: The eap docker image has "/opt/eap/standalone/deployments" specified as deployment path in the labels {code:JavaScript|title=oc get istag eap-app:latest --output=json} { "kind": "ImageStreamTag", "apiVersion": "v1", "metadata": { "name": "eap-app:latest", ... "Labels": { ... "org.jboss.deployments-dir": "/opt/eap/standalone/deployments", ... } {code} was: # ASSERT: make sure that you have an eap based app running # EXEC: launch server adapter wizard and pick OpenShift 3 server adapter. Pick your connection and get to the next page. # ASSERT: New Server dialog shows up # EXEC: inspect the Pod Deployment Path Result: The wizard report "/opt/app-root/src" Expected result: The eap docker image has "/opt/eap/standalone/deployments" specified as deployment path in the labels {code;oc get istag eap-app:latest --output=json} { "kind": "ImageStreamTag", "apiVersion": "v1", "metadata": { "name": "eap-app:latest", ... "Labels": { ... "org.jboss.deployments-dir": "/opt/eap/standalone/deployments", ... {code} > Server adapter wizard: pod deployment path is always default (/opt/app-root/src) > -------------------------------------------------------------------------------- > > Key: JBIDE-21703 > URL: https://issues.jboss.org/browse/JBIDE-21703 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21625) Server adapter: Enable debug mode on OpenShift servers

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21625?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21625: ------------------------------------- For nodejs apps, DEV_MODE=true shuld be added to the env vars. AFAIK, there's no matching debug port to expose > Server adapter: Enable debug mode on OpenShift servers > ------------------------------------------------------ > > Key: JBIDE-21625 > URL: https://issues.jboss.org/browse/JBIDE-21625 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Need to easily enable debug mode on EAP/Node images. That should allow hot reloading of server.js or java classes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21702) For Java projects, automatically attach a remote debugger to the OpenShift debug port

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21702: ----------------------------------- Summary: For Java projects, automatically attach a remote debugger to the OpenShift debug port Key: JBIDE-21702 URL: https://issues.jboss.org/browse/JBIDE-21702 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Fred Bricon Given a local debug port, we should automatically attach a remote debugger to that port (similar to what is described in http://tools.jboss.org/documentation/howto/openshift_debug.html#idedebugger) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21703) Server adapter wizard: pod deployment path is always default (/opt/app-root/src)

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21703: ---------------------------------------- Summary: Server adapter wizard: pod deployment path is always default (/opt/app-root/src) Key: JBIDE-21703 URL: https://issues.jboss.org/browse/JBIDE-21703 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Andre Dietisheim Priority: Critical -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21701) Enable port forwarding on a given pod and a given debug port

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21701: ----------------------------------- Summary: Enable port forwarding on a given pod and a given debug port Key: JBIDE-21701 URL: https://issues.jboss.org/browse/JBIDE-21701 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Fred Bricon Given a remote debug port, we need to ensure to programmatically enable port forwarding on a pod, return the matching local debug port (named debug). The local port could be determined as the next available free port, or read from the server adapter's preferences. But that latter case would also require adding some UI to let a user set the local port. That could be done in a later iteration. If port forwarding is already enabled on the remote pod, then the current local debug port should be returned -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19910) Add w3 schemes to XML catalog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19910?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19910: -------------------------------- Fix Version/s: 4.3.1.CR1 4.4.0.Alpha1 (was: 4.3.x) > Add w3 schemes to XML catalog > ----------------------------- > > Key: JBIDE-19910 > URL: https://issues.jboss.org/browse/JBIDE-19910 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Rastislav Wagner > Assignee: Rob Stryker > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > We should add w3 schemes which are used in our quickstarts/examples to XML catalog because: > 1) w3 servers are intentionally slow > 2) it seems that wsdl validator does no caching of previously downloaded schemes > I will take a look at examples and list schemes here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21700) Listen to pod redeployment after changing deployment configuration

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21700: ----------------------------------- Summary: Listen to pod redeployment after changing deployment configuration Key: JBIDE-21700 URL: https://issues.jboss.org/browse/JBIDE-21700 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Fred Bricon We need an easy way to detect a deployment configuration change triggered a new deployment and then be notified of its completion -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21699) Enable debug mode on deployment config

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21699: ----------------------------------- Summary: Enable debug mode on deployment config Key: JBIDE-21699 URL: https://issues.jboss.org/browse/JBIDE-21699 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Reporter: Fred Bricon Priority: Critical When clicking on the Debug button of the server adapter, the Debug variables should be set, if necessary. The remote debug port could be read from server adapter preferences, default to 8787 {code} { "name" : "debug", "containerPort" : 8787, "protocol" : "TCP" } {code} * and to spec.containers.env: {code} { "name" : "DEBUG", "value" : "true" }, { "name" : "DEBUG_PORT", "value" : "8787" } {code} If the remote debug port was already set (possibly to another value), then it should be returned -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21625) Server adapter: Enable debug mode on OpenShift servers

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21625?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21625: ------------------------------------- So basically, what we need to do is, make it so that when a user clicks on the debug button on the server adapter, the following happens : - modify the deployment configuration to add DEBUG, DEBUG_PORT env vars, add the debug port if necessary - wait for a new deployment to set up a new pod, if the current pod is not setup to debug mode - enable port forwarding between the (new) pod debug port and a local debug port (unless port forwarding as already been setup) - attach a remote debugger to the local debug port (what if it's not a java process?) > Server adapter: Enable debug mode on OpenShift servers > ------------------------------------------------------ > > Key: JBIDE-21625 > URL: https://issues.jboss.org/browse/JBIDE-21625 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Need to easily enable debug mode on EAP/Node images. That should allow hot reloading of server.js or java classes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21666) Properties view: Set correct OpenShift resource name for Repplication controller in properties view

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21666?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21666: ------------------------------------- Summary: Properties view: Set correct OpenShift resource name for Repplication controller in properties view (was: Set correct OpenShift resource name for Repplication controller in properties view) > Properties view: Set correct OpenShift resource name for Repplication controller in properties view > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-21666 > URL: https://issues.jboss.org/browse/JBIDE-21666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > Fix For: 4.4.x > > > At the moment we have following OpenShift resources listed for a project in Properties view: > * Builds > * Build Configs > * Deployment Configs > * Pods > * Deployments > * Image Streams > * Routes > * Services > What is misleading is having "Deployment Configs" and "Deployments". We are trying to copy web-UI, as far as I know. But in the web-UI under Deployments are placed "Deployment Configs". We, under "Deployments" in properties view, have "Replication Controllers". So its misleading for me. I think we should rename our Deployment Configs to Deployment and our Deployments to Replication Controllers, which are missing in web-ui because the most significant functionality accessible via Replication Controllers is editable in web-ui through overview page (e.g spinner for amount of pods). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016