[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-24491.
---------------------------------
Resolution: Done
much better logging is present.
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.1.Final
>
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-24491:
--------------------------------
Fix Version/s: 4.5.1.Final
(was: 4.5.x)
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.1.Final
>
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25167) CDK 3.2+ adapter is created automatically even if I have CDK 3.1.1 installed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25167?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-25167:
--------------------------------
Fix Version/s: 4.5.1.Final
Sprint: devex #138 September 2017
> CDK 3.2+ adapter is created automatically even if I have CDK 3.1.1 installed
> ----------------------------------------------------------------------------
>
> Key: JBIDE-25167
> URL: https://issues.jboss.org/browse/JBIDE-25167
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.5.1.Final
>
>
> I installed devstudio 11.1.0.AM3 B1225 and when I launched it there was a cdk server adapter already set up. That's completely normal. But what's wrong is that it's the new 3.2+ adapter whereas what I have actually installed in ~/.minishift is version 3.1.1.
> The runtime detection should be able to detect the version in ~/.minishift/cdk and return a match only if the version is compatible with the given adapter.
> [~jkopriva] says cdk 3.1.1 cannot be launched with cdk 3.2+ adapter. I cannot really check that myself because my server adapter doesn't have minishift binary set up by default and you validate the version in the server editor, so I can't use 3.1.1 with the 3.2+ adapter.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25192) Error when eclipse environment has MINISHIFT_HOME different from adapter
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25192?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-25192:
--------------------------------
Sprint: devex #138 September 2017
> Error when eclipse environment has MINISHIFT_HOME different from adapter
> ------------------------------------------------------------------------
>
> Key: JBIDE-25192
> URL: https://issues.jboss.org/browse/JBIDE-25192
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.AM3
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.5.1.Final
>
>
> Steps to reproduce:
> 1) Start eclipse with an environment that has a MINISHIFT_HOME set to one value
> 2) Create a server adapter with the default minishift home ~/.minishift (ie make no changes)
> 3) via cmdline, try to setup cdk using cdk 3.2a and the .minishift home folder
> 4) Try to start the server
> Expected results: Server starts as expected
> Actual results: No minishift_home is set. The eclipse environment's minishift home is used. The server attempts to start and tells you to call setup-cdk. The user gets very confused, because the server editor clearly is using ~/.minishift as the home.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25171) Changing value of 'Minishift profile' in CDK 3.2.+ server adapter should be reflected in Launch Configuration
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25171?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-25171:
--------------------------------
Sprint: devex #138 September 2017
> Changing value of 'Minishift profile' in CDK 3.2.+ server adapter should be reflected in Launch Configuration
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25171
> URL: https://issues.jboss.org/browse/JBIDE-25171
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.5.1.AM3
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.5.1.Final
>
>
> Changing value of 'Minishift profile' field should get propagated into Launch configuration of CDK 3.2+ server adapter.
> Also, if user leaves Minishift Profile field empty during filling up the wizard, and then he sets up the profile value in CDK 3.2 server adapter editor, it should be reflected in launch configuration (simply add "--profile someValue") arguments after save.
> [~rob.stryker], could you, please, take a look here? Thanks!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months