[ https://issues.jboss.org/browse/JBIDE-21625?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21625 at 2/5/16 4:29 PM: ------------------------------------------------------------------ As specificed in CLOUD-243: Enabling debugging in our eap-images works via an env var {code} com.redhat.dev-mode com.redhat.dev-mode.port {code} In [oc|https://docs.openshift.com/enterprise/3.0/dev_guide/environment_variab...] one can do {code} $ oc env <object-selection> KEY_1=VAL_1 ... KEY_N=VAL_N [<set-env-options>] [<common-options>] {code} Those get picked on pod deployment. So we can change the deployment config resource and start for the triggered build to finish or change the number of replicas 1->0->1 {quote} (06:19:17 PM) kconner: adietisheim: The env needs to be set when the pod starts, you may find that modifying the dc will redeploy it {quote} You can achieve this by changing the deployment config in Eclipse: * for the deployment config changes, add to spec.containers.ports : {code} { "name" : "debug", "containerPort" : 9876, "protocol" : "TCP" } {code} * and to spec.containers.env: {code} { "name" : "DEBUG", "value" : "true" }, { "name" : "DEBUG_PORT", "value" : "9876" } {code} was (Author: adietish): As specificed in CLOUD-243: Enabling debugging in our eap-images works via an env var {code} com.redhat.dev-mode com.redhat.dev-mode.port {code} In [oc|https://docs.openshift.com/enterprise/3.0/dev_guide/environment_variab...] one can do {code} $ oc env <object-selection> KEY_1=VAL_1 ... KEY_N=VAL_N [<set-env-options>] [<common-options>] {code} Those get picked on pod deployment. So we can change the deployment config resource and start for the triggered build to finish or change the number of replicas 1->0->1 {quote} (06:19:17 PM) kconner: adietisheim: The env needs to be set when the pod starts, you may find that modifying the dc will redeploy it {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)