[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:
-----------------------------------
Attachment: screenshot-3.png
> 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: Dockerfile, Problem_Description.pdf, screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> 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:
-----------------------------------
Attachment: screenshot-2.png
> 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: Dockerfile, Problem_Description.pdf, screenshot-1.png, screenshot-2.png
>
>
> 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:
-----------------------------------
Attachment: screenshot-1.png
> 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: Dockerfile, Problem_Description.pdf, screenshot-1.png
>
>
> 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:
-----------------------------------
Attachment: Dockerfile
> 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: Dockerfile, 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 4:05 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=expected: DeploymentConfig with ImageChange trigger}
"triggers" : [
{"type" : "ConfigChange"},
{
"type" : "ImageChange",
"imageChangeParams" : {
"automatic" : true,
"containerNames" : ["openshift-tomcat"],
"from" : {
"kind" : "ImageStreamTag",
"namespace" : "openshif-tomcat",
"name" : "openshift-tomcat:3"
},
"lastTriggeredImage" : "adietish/openshift-tomcat@sha256:95f62ac5028b9971ccc3279fea2a225a1bc89178c6b117fbb4f4ca4f8793538c"
}
}
],
{code}
{code:title=present: 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=expected: DeploymentConfig with ImageChange trigger}
"triggers": [
{
"type": "ImageChange",
"imageChangeParams": {
"automatic": true,
"from": {
"kind": "ImageStreamTag",
"name": "origin-ruby-sample:latest"
},
"containerNames": [
"helloworld"
]
}
}
]
{code}
{code:title=present: 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.
> 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-26673) Dependency on org.eclipse.rse.ui 3.3 affects installation
by Manuel Parrao (Jira)
[ https://issues.jboss.org/browse/JBIDE-26673?page=com.atlassian.jira.plugi... ]
Manuel Parrao commented on JBIDE-26673:
---------------------------------------
Hi,
Doing it from the eclipse marketplace seems it's using this update site:
download.jboss.org/jbosstools/oxygen/stable/updates
Digging in there I found this URL that contains rse 3.3, not sure if it's where it is bringing it from
https://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolsta...
Also the rse 4.6 is comming for the other plugin that is conflicting in the install with JBOSS I'm currently investigating where it comes from because as you mentioned seems 4.5.100 is the latest release.
> Dependency on org.eclipse.rse.ui 3.3 affects installation
> ---------------------------------------------------------
>
> Key: JBIDE-26673
> URL: https://issues.jboss.org/browse/JBIDE-26673
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Environment: This happens on eclipse Luna and Oxygen installing from the marketplace or directly from eclipse when creating a new JBOSS server
> Reporter: Manuel Parrao
> Priority: Minor
>
> I have a product that uses different plugins and some of them failed to be installed if JBOSS tools are installed first since JBOSS tools has a dependency on org.eclipse.rse.ui V3.3 and the other plugins I use work with org.eclipse.rse.ui V4.4 and org.eclipse.rse.ui V4.6. On the other hand if I install first the other plugins and then try to install JBOSS tools, JBOSS does not get installed due the same dependency issue.
> Would it be possible to modify the manifest to accept org.eclipse.rse.ui 3.3 or later?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26673) Dependency on org.eclipse.rse.ui 3.3 affects installation
by Nick Boldt (Jira)
[ https://issues.jboss.org/browse/JBIDE-26673?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26673:
------------------------------------
Latest JBT/Studio targetplaform repo is here:
https://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4....
And there's no rsu.ui 3.3 in there, but rather org.eclipse.rse.ui_4.5.100.201901312252.jar
So... I'd say the problem might be at your end. What update sites do you have configured in your Eclipse instance?
> Dependency on org.eclipse.rse.ui 3.3 affects installation
> ---------------------------------------------------------
>
> Key: JBIDE-26673
> URL: https://issues.jboss.org/browse/JBIDE-26673
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Environment: This happens on eclipse Luna and Oxygen installing from the marketplace or directly from eclipse when creating a new JBOSS server
> Reporter: Manuel Parrao
> Priority: Minor
>
> I have a product that uses different plugins and some of them failed to be installed if JBOSS tools are installed first since JBOSS tools has a dependency on org.eclipse.rse.ui V3.3 and the other plugins I use work with org.eclipse.rse.ui V4.4 and org.eclipse.rse.ui V4.6. On the other hand if I install first the other plugins and then try to install JBOSS tools, JBOSS does not get installed due the same dependency issue.
> Would it be possible to modify the manifest to accept org.eclipse.rse.ui 3.3 or later?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26673) Dependency on org.eclipse.rse.ui 3.3 affects installation
by Nick Boldt (Jira)
[ https://issues.jboss.org/browse/JBIDE-26673?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26673:
------------------------------------
In the words of Barney from HIMYM, "Haaaaaaave ya met rse.ui 4.5.100?"
https://ci.eclipse.org/tm/job/tm-terminal-rse_master/lastSuccessfulBuild/...
In the words of Sigourney Weaver in Ghostbusters, "There is no 4.6, only 4.5.100".
> Dependency on org.eclipse.rse.ui 3.3 affects installation
> ---------------------------------------------------------
>
> Key: JBIDE-26673
> URL: https://issues.jboss.org/browse/JBIDE-26673
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Environment: This happens on eclipse Luna and Oxygen installing from the marketplace or directly from eclipse when creating a new JBOSS server
> Reporter: Manuel Parrao
> Priority: Minor
>
> I have a product that uses different plugins and some of them failed to be installed if JBOSS tools are installed first since JBOSS tools has a dependency on org.eclipse.rse.ui V3.3 and the other plugins I use work with org.eclipse.rse.ui V4.4 and org.eclipse.rse.ui V4.6. On the other hand if I install first the other plugins and then try to install JBOSS tools, JBOSS does not get installed due the same dependency issue.
> Would it be possible to modify the manifest to accept org.eclipse.rse.ui 3.3 or later?
--
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:37 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=expected: DeploymentConfig with ImageChange trigger}
"triggers": [
{
"type": "ImageChange",
"imageChangeParams": {
"automatic": true,
"from": {
"kind": "ImageStreamTag",
"name": "origin-ruby-sample:latest"
},
"containerNames": [
"helloworld"
]
}
}
]
{code}
{code:title=present: 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=expected: DeploymentConfig with ImageChange trigger}
"triggers": [
{
"type": "ImageChange",
"imageChangeParams": {
"automatic": true,
"from": {
"kind": "ImageStreamTag",
"name": "origin-ruby-sample:latest"
},
"containerNames": [
"helloworld"
]
}
}
]
{code}
{code:title=present: 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.
> 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:36 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=expected: DeploymentConfig with ImageChange trigger}
"triggers": [
{
"type": "ImageChange",
"imageChangeParams": {
"automatic": true,
"from": {
"kind": "ImageStreamTag",
"name": "origin-ruby-sample:latest"
},
"containerNames": [
"helloworld"
]
}
}
]
{code}
{code:title=present: 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 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.
> 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