-
Feature Request
-
Resolution: Done
-
Major
-
4.5.1.AM2
-
devex #141 December 2017
-
13
in JBIDE-24491 we introduced the ability to look up the docker registry in the cdk:
We should also test that the docker registry in the connection is updated when the cdk starts up (see JBIDE-25046).
We should now also have this covered by bot-tests. Especially the bugs found in JBIDE-25046 and JBIDE-25049 should be covered.
- is related to
-
JBIDE-25046 Can't find CDK for registry discovery when 2 connections are defined for CDK
- Closed
-
JBIDE-25049 Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
- Closed
-
JBIDE-25438 Refactor CDK itests to be more stable against CDK starts that fail sometimes
- Closed
- relates to
-
JBIDE-24491 CDK Server adapter: allow users to look up the address of the docker registry
- Closed