[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ]
André Dietisheim edited comment on JBDS-4777 at 6/14/19 2:35 PM:
-----------------------------------------------------------------
Things fail in the Eclipse server adapter because the tooling is unable to determine the docker image that the labels should be extracted from:
Our current strategy is to get the docker image from a deployment config/ImageChange trigger. This worked fine in the s2i use case that was more common to us.
In this particular case where a pre-built docker image is deployed *ImageChange* triggers are not present. The triggers that are present are *ConfigChange* triggers which lack the docker image uri.
{code:title=DeploymentConfig with ConfigChange trigger}
"triggers": [
{
"type": "ConfigChange"
}
]
{code}
{code:title=our code that retrieves the docker image - https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or...
IDeploymentImageChangeTrigger trigger = getImageChangeTrigger(dc.getTriggers());
if (trigger == null) {
return null;
}
DockerImageURI uri = trigger.getFrom();
{code}
A temporary work around could be to use s2i instead of a pre-built docker image.
was (Author: adietish):
Things fail in the Eclipse server adapter because the tooling is unable to determine the docker image that the labels should be extracted from:
Our current strategy is to get the docker image from a deployment config/ImageChange trigger. This worked fine in the s2i use case that was more common to us.
In this particular case where a pre-built docker image is deployed *ImageChange* triggers are not present. The triggers that are present are *ConfigChange* triggers which lack the docker image uri.
{code:title=DeploymentConfig}
"triggers": [
{
"type": "ConfigChange"
}
]
{code}
{code:title=our code that retrieves the docker image - https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or...
IDeploymentImageChangeTrigger trigger = getImageChangeTrigger(dc.getTriggers());
if (trigger == null) {
return null;
}
DockerImageURI uri = trigger.getFrom();
{code}
A temporary work around could be to use s2i instead of a pre-built docker image.
> Please document procedure (if possible) for defining Debug port, Deployment path
> --------------------------------------------------------------------------------
>
> Key: JBDS-4777
> URL: https://issues.jboss.org/browse/JBDS-4777
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 12.11.0.GA
> Environment: CodeReady Studio 12.11
> Reporter: Rick Wagner
> Assignee: Jeff MAURY
> Priority: Major
> Labels: openshift
> Fix For: 12.x
>
> Attachments: Problem_Description.pdf
>
>
> Please document procedure for pre-filling the following in Adapter Server Settings:
> - Pod Deployment Path
> - Debugging Key
> - Debugging Port
> Can this be done via image Labels from an imported Docker image?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ]
André Dietisheim edited comment on JBDS-4777 at 6/14/19 2:34 PM:
-----------------------------------------------------------------
Things fail in the Eclipse server adapter because the tooling is unable to determine the docker image that the labels should be extracted from:
Our current strategy is to get the docker image from a deployment config/ImageChange trigger. This worked fine in the s2i use case that was more common to us.
In this particular case where a pre-built docker image is deployed *ImageChange* triggers are not present. The triggers that are present are *ConfigChange* triggers which lack the docker image uri.
{code:title=DeploymentConfig}
"triggers": [
{
"type": "ConfigChange"
}
]
{code}
{code:title=our code that retrieves the docker image - https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or...
IDeploymentImageChangeTrigger trigger = getImageChangeTrigger(dc.getTriggers());
if (trigger == null) {
return null;
}
DockerImageURI uri = trigger.getFrom();
{code}
A temporary work around could be to use s2i instead of a pre-built docker image.
was (Author: adietish):
Things fail in the Eclipse server adapter because the tooling is unable to determine the docker image that the labels should be extracted from:
Our current strategy is to get the docker image from a deployment config/image change trigger. This worked fine in the s2i use case that was more common to us. In this particular case where a pre-built docker image is deployed image change triggers are not present. The triggers that are present are ConfigChange triggers which lack the docker image uri.
{code:title=DeploymentConfig}
"triggers": [
{
"type": "ConfigChange"
}
]
{code}
{code:title=our code that retrieves the docker image - https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or...
IDeploymentImageChangeTrigger trigger = getImageChangeTrigger(dc.getTriggers());
if (trigger == null) {
return null;
}
DockerImageURI uri = trigger.getFrom();
{code}
A temporary work around could be to use s2i instead of a pre-built docker image.
> Please document procedure (if possible) for defining Debug port, Deployment path
> --------------------------------------------------------------------------------
>
> Key: JBDS-4777
> URL: https://issues.jboss.org/browse/JBDS-4777
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 12.11.0.GA
> Environment: CodeReady Studio 12.11
> Reporter: Rick Wagner
> Assignee: Jeff MAURY
> Priority: Major
> Labels: openshift
> Fix For: 12.x
>
> Attachments: Problem_Description.pdf
>
>
> Please document procedure for pre-filling the following in Adapter Server Settings:
> - Pod Deployment Path
> - Debugging Key
> - Debugging Port
> Can this be done via image Labels from an imported Docker image?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ]
André Dietisheim edited comment on JBDS-4777 at 6/14/19 2:33 PM:
-----------------------------------------------------------------
Things fail in the Eclipse server adapter because the tooling is unable to determine the docker image that the labels should be extracted from:
Our current strategy is to get the docker image from a deployment config/image change trigger. This worked fine in the s2i use case that was more common to us. In this particular case where a pre-built docker image is deployed image change triggers are not present. The triggers that are present are ConfigChange triggers which lack the docker image uri.
{code:title=DeploymentConfig}
"triggers": [
{
"type": "ConfigChange"
}
]
{code}
{code:title=our code that retrieves the docker image - https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or...
IDeploymentImageChangeTrigger trigger = getImageChangeTrigger(dc.getTriggers());
if (trigger == null) {
return null;
}
DockerImageURI uri = trigger.getFrom();
{code}
A temporary work around could be to use s2i instead of a pre-built docker image.
was (Author: adietish):
Things fail in the Eclipse server adapter because the tooling is unable to determine the docker image that the labels should be extracted from:
Our current strategy is to get the docker image from a deployment config/image change trigger. This worked fine in the s2i use case that was more common to us. In this particular case where a pre-built docker image is deployed image change triggers are not present. The triggers that are present are ConfigChange triggers which lack the docker image uri.
{code:title=DeploymentConfig}
"triggers": [
{
"type": "ConfigChange"
}
]
{code}
{code:title=https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.core/src/org/jboss/tools/openshift/core/server/DockerImageLabels.java#L141}
IDeploymentImageChangeTrigger trigger = getImageChangeTrigger(dc.getTriggers());
if (trigger == null) {
return null;
}
DockerImageURI uri = trigger.getFrom();
{code}
A temporary work around could be to use s2i instead of a pre-built docker image.
> Please document procedure (if possible) for defining Debug port, Deployment path
> --------------------------------------------------------------------------------
>
> Key: JBDS-4777
> URL: https://issues.jboss.org/browse/JBDS-4777
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 12.11.0.GA
> Environment: CodeReady Studio 12.11
> Reporter: Rick Wagner
> Assignee: Jeff MAURY
> Priority: Major
> Labels: openshift
> Fix For: 12.x
>
> Attachments: Problem_Description.pdf
>
>
> Please document procedure for pre-filling the following in Adapter Server Settings:
> - Pod Deployment Path
> - Debugging Key
> - Debugging Port
> Can this be done via image Labels from an imported Docker image?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ]
André Dietisheim edited comment on JBDS-4777 at 6/14/19 2:32 PM:
-----------------------------------------------------------------
Things fail in the Eclipse server adapter because the tooling is unable to determine the docker image that the labels should be extracted from:
Our current strategy is to get the docker image from a deployment config/image change trigger. This worked fine in the s2i use case that was more common to us. In this particular case where a pre-built docker image is deployed image change triggers are not present. The triggers that are present are ConfigChange triggers which lack the docker image uri.
{code:title=DeploymentConfig}
"triggers": [
{
"type": "ConfigChange"
}
]
{code}
{code:title=https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.core/src/org/jboss/tools/openshift/core/server/DockerImageLabels.java#L141}
IDeploymentImageChangeTrigger trigger = getImageChangeTrigger(dc.getTriggers());
if (trigger == null) {
return null;
}
DockerImageURI uri = trigger.getFrom();
{code}
A temporary work around could be to use s2i instead of a pre-built docker image.
was (Author: adietish):
Things fail in the Eclipse server adapter because the tooling is unable to determine the docker image that the labels should be extracted from:
Our current strategy is to get the docker image from a deployment config/image change trigger. This worked fine in the s2i use case that was more common to us. In this particular case where a pre-built docker image is deployed image change triggers are not present. The triggers that the deployment config has are config change triggers which lack the docker image uri.
{code:title=DeploymentConfig}
"triggers": [
{
"type": "ConfigChange"
}
]
{code}
{code:title=https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.core/src/org/jboss/tools/openshift/core/server/DockerImageLabels.java#L141}
IDeploymentImageChangeTrigger trigger = getImageChangeTrigger(dc.getTriggers());
if (trigger == null) {
return null;
}
DockerImageURI uri = trigger.getFrom();
{code}
A temporary work around could be to use s2i instead of a pre-built docker image.
> Please document procedure (if possible) for defining Debug port, Deployment path
> --------------------------------------------------------------------------------
>
> Key: JBDS-4777
> URL: https://issues.jboss.org/browse/JBDS-4777
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 12.11.0.GA
> Environment: CodeReady Studio 12.11
> Reporter: Rick Wagner
> Assignee: Jeff MAURY
> Priority: Major
> Labels: openshift
> Fix For: 12.x
>
> Attachments: Problem_Description.pdf
>
>
> Please document procedure for pre-filling the following in Adapter Server Settings:
> - Pod Deployment Path
> - Debugging Key
> - Debugging Port
> Can this be done via image Labels from an imported Docker image?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26678) Project Explorer in RH CodeReady Studio shows incorrect project items hierarchy
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26678?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka commented on JBIDE-26678:
-----------------------------------------
*Update*: I have found out, that just a simple Refresh from Project Explorer fixes the misleading file items representation in Project Explorer. But it is a bug after all, user have to refresh and it should work right without refreshing.
> Project Explorer in RH CodeReady Studio shows incorrect project items hierarchy
> -------------------------------------------------------------------------------
>
> Key: JBIDE-26678
> URL: https://issues.jboss.org/browse/JBIDE-26678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Environment: OS X 10.14.5, CodeReady Studio Version: 12.12.0.AM1, java 8
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: pe.png, terminal.png
>
>
> Project Explorer in RH CodeReady Studio shows incorrect project items hierarchy, which is misleading and causes problems when accessing the items via RedDeer Project Explorer classes
> - after creating new CDI web project in the RH CodeReady Studio and after creating several packages in the project, the Project Explorer shows incorrect tree hierarchy according to:
> * how it should be (according to common sense)
> * how it is displayed when working with simple *Java project* in RH CodeReady Studio/Eclipse (after creating several packages)
> * project files hierarchy stored on the disk (see the *terminal.png* image in the attachment listing the content of the *src* folder on the disk)
> - look at the *pe.png* image in the attachment to see that firstly created packed placed in the *src* folder, other packages on the same level as *src* folder
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26678) Project Explorer in RH CodeReady Studio shows incorrect project items hierarchy
by Zbyněk Červinka (Jira)
Zbyněk Červinka created JBIDE-26678:
---------------------------------------
Summary: Project Explorer in RH CodeReady Studio shows incorrect project items hierarchy
Key: JBIDE-26678
URL: https://issues.jboss.org/browse/JBIDE-26678
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi
Environment: OS X 10.14.5, CodeReady Studio Version: 12.12.0.AM1, java 8
Reporter: Zbyněk Červinka
Attachments: pe.png, terminal.png
Project Explorer in RH CodeReady Studio shows incorrect project items hierarchy, which is misleading and causes problems when accessing the items via RedDeer Project Explorer classes
- after creating new CDI web project in the RH CodeReady Studio and after creating several packages in the project, the Project Explorer shows incorrect tree hierarchy according to:
* how it should be (according to common sense)
* how it is displayed when working with simple *Java project* in RH CodeReady Studio/Eclipse (after creating several packages)
* project files hierarchy stored on the disk (see the *terminal.png* image in the attachment listing the content of the *src* folder on the disk)
- look at the *pe.png* image in the attachment to see that firstly created packed placed in the *src* folder, other packages on the same level as *src* folder
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ]
André Dietisheim commented on JBDS-4777:
----------------------------------------
Interesting enough openshift/wildfly-160-centos7 only has the deployments-dir while the image is marked as s2i-base-container (com.redhat.component):
{code}
"com.redhat.component": "s2i-base-container",
"com.redhat.deployments-dir": "/wildfly/standalone/deployments",
{code}
on the other hand openshift/nodejs-010-centos7 has all 3 of them (and has no labelling for being a s2i base container):
{code}
"com.redhat.deployments-dir": "/opt/app-root/src",
"com.redhat.dev-mode": "DEV_MODE:false",
"com.redhat.dev-mode.port": "DEBUG_PORT:5858",
{code}
> Please document procedure (if possible) for defining Debug port, Deployment path
> --------------------------------------------------------------------------------
>
> Key: JBDS-4777
> URL: https://issues.jboss.org/browse/JBDS-4777
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 12.11.0.GA
> Environment: CodeReady Studio 12.11
> Reporter: Rick Wagner
> Assignee: Jeff MAURY
> Priority: Major
> Labels: openshift
> Fix For: 12.x
>
> Attachments: Problem_Description.pdf
>
>
> Please document procedure for pre-filling the following in Adapter Server Settings:
> - Pod Deployment Path
> - Debugging Key
> - Debugging Port
> Can this be done via image Labels from an imported Docker image?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ]
André Dietisheim updated JBDS-4777:
-----------------------------------
Fix Version/s: 12.x
> Please document procedure (if possible) for defining Debug port, Deployment path
> --------------------------------------------------------------------------------
>
> Key: JBDS-4777
> URL: https://issues.jboss.org/browse/JBDS-4777
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 12.11.0.GA
> Environment: CodeReady Studio 12.11
> Reporter: Rick Wagner
> Assignee: Jeff MAURY
> Priority: Major
> Labels: openshift
> Fix For: 12.x
>
> Attachments: Problem_Description.pdf
>
>
> Please document procedure for pre-filling the following in Adapter Server Settings:
> - Pod Deployment Path
> - Debugging Key
> - Debugging Port
> Can this be done via image Labels from an imported Docker image?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months