[JBoss JIRA] (JBIDE-25046) Can't find CDK for registry discovery when 2 connections are defined for CDK
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25046?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-25046:
------------------------------------
Side note: if the admin connection is created after the CDK server has been started, then the discover will work.
> Can't find CDK for registry discovery when 2 connections are defined for CDK
> ----------------------------------------------------------------------------
>
> Key: JBIDE-25046
> URL: https://issues.jboss.org/browse/JBIDE-25046
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: cdk, cdk_server_adapter_, explorer, openshift, openshift_v3
> Fix For: 4.5.x
>
>
> EXEC: define an Openshift connection for CDK/admin
> EXEC: define an Openshift connection for CDK/developer
> EXEC: define a CDK3 server
> EXEC: start the CDK 3 server
> ASSERT: the CDK/admin OS3 connection is updated (registry not empty)
> ASSERT: the CDK/developer OS3 connection is not updated (registry empty)
> EXEC: on the CDK/developer OS3 connection, click the DIscover buttoon
> ASSERT: the registry URL is updated, not the error dialog is displayed
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25047) Connection wizard: correct advanced buttons to be equal in width
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25047?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25047:
-------------------------------------
Summary: Connection wizard: correct advanced buttons to be equal in width (was: Connection wizard: correct advanced buttons to be equal in (horiz.) width)
> Connection wizard: correct advanced buttons to be equal in width
> ----------------------------------------------------------------
>
> Key: JBIDE-25047
> URL: https://issues.jboss.org/browse/JBIDE-25047
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: connection_wizard, openshift_v3, usability
> Fix For: 4.5.x
>
> Attachments: corrected-button-width.png, image-2017-09-18-11-44-28-929.png
>
>
> # EXEC: open up connection wizard (either by trying to create a new or edit an existing connection
> # EXEC: hit "Advanced"
> Result
> The buttons "Browse" and "Discover" have different width resulting in an ugly UI
> !image-2017-09-18-11-44-28-929.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25049:
-------------------------------------
Labels: connection_wizard openshift_v3 (was: )
> Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25049
> URL: https://issues.jboss.org/browse/JBIDE-25049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.x
>
> Attachments: screenshot-1.png
>
>
> # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry.
> {code}
> [adietish@localhost minishift]$ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
> # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
> # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
> # EXEC: edit the OpenShift connection
> # ASSERT: connection wizard shows up
> # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
> # EXEC: hit "Discover"
> Result
> An error dialog shows up telling you no registry provider could be found
> !screenshot-1.png!
>
> the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25049:
-------------------------------------
Description:
# ASSERT: make sure that you have a minishift that does *NOT* have a docker registry.
{code}
[adietish@localhost minishift]$ ./minishift openshift registry
No information found for 'service/docker-registry'
{code}
# ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
# ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
# EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
# EXEC: edit the OpenShift connection
# ASSERT: connection wizard shows up
# EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
# EXEC: hit "Discover"
Result
An error dialog shows up telling you no registry provider could be found
!screenshot-1.png!
the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
was:
# ASSERT: make sure that you have a minishift that does *NOT* have a docker registry.
{code}
[adietish@localhost minishift]$ ./minishift openshift registry
No information found for 'service/docker-registry'
{code}
# ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
# ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
# EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
# EXEC: edit the OpenShift connection
# ASSERT: connection wizard shows up
# EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
# EXEC: hit "Discover"
Result
An error dialog shows up telling you no registry provider could be found
!screenshot-1.png!
> Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25049
> URL: https://issues.jboss.org/browse/JBIDE-25049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.x
>
> Attachments: screenshot-1.png
>
>
> # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry.
> {code}
> [adietish@localhost minishift]$ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
> # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
> # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
> # EXEC: edit the OpenShift connection
> # ASSERT: connection wizard shows up
> # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
> # EXEC: hit "Discover"
> Result
> An error dialog shows up telling you no registry provider could be found
> !screenshot-1.png!
>
> the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25012) Hibernate: refactor integration tests for use with RedDeer 2.0
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25012?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-25012.
------------------------------------
> Hibernate: refactor integration tests for use with RedDeer 2.0
> --------------------------------------------------------------
>
> Key: JBIDE-25012
> URL: https://issues.jboss.org/browse/JBIDE-25012
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: hibernate, integration-tests
> Affects Versions: 4.5.1.AM1
> Reporter: Nick Boldt
> Assignee: Rastislav Wagner
> Priority: Critical
> Fix For: 4.5.1.AM2
>
>
> A number of hibernate plugins require reddeer 1.2 and need to be migrated to use 2.0.
> {code}
> ** [1] ./itests/org.jboss.tools.hibernate.ui.bot.test/META-INF/MANIFEST.MF **
> 12- org.jboss.tools.common.ui,
> 13- org.eclipse.datatools.connectivity,
> 14: org.jboss.tools.hibernate.reddeer;bundle-version="[5.2.0,5.3.0)",
> 15: org.jboss.reddeer.go;bundle-version="[1.2.2,2.0.0)",
> 16: org.jboss.tools.common.reddeer,
> 17- org.eclipse.m2e.maven.indexer;bundle-version="1.7.1",
> 18- org.eclipse.m2e.maven.runtime;bundle-version="1.7.1",
> ** [2] ./test-framework/org.jboss.tools.hibernate.reddeer/META-INF/MANIFEST.MF **
> 2-Bundle-ManifestVersion: 2
> 3-Bundle-Name: RedDeer API for Hibernate UI Tests
> 4:Bundle-SymbolicName: org.jboss.tools.hibernate.reddeer
> 5-Bundle-Version: 5.2.1.qualifier
> 6:Bundle-Activator: org.jboss.tools.hibernate.reddeer.Activator
> 7-Require-Bundle: org.eclipse.ui,
> 8- org.eclipse.core.runtime,
> --
> 10- org.junit,
> 11- org.eclipse.core.resources,
> 12: org.jboss.reddeer.go;bundle-version="[1.2.2,2.0.0)",
> 13: org.jboss.tools.common.reddeer;bundle-version="[3.9.0,3.10.0)"
> 14-Bundle-ActivationPolicy: lazy
> 15-Bundle-RequiredExecutionEnvironment: JavaSE-1.8
> 16:Export-Package: org.jboss.tools.hibernate.reddeer,
> 17: org.jboss.tools.hibernate.reddeer.console,
> 18: org.jboss.tools.hibernate.reddeer.dialog,
> 19: org.jboss.tools.hibernate.reddeer.editor,
> 20: org.jboss.tools.hibernate.reddeer.perspective,
> 21: org.jboss.tools.hibernate.reddeer.view,
> 22: org.jboss.tools.hibernate.reddeer.wizard,
> 23: org.jboss.tools.hibernate.reddeer.condition,
> 24: org.jboss.tools.hibernate.reddeer.console.wizards,
> 25: org.jboss.tools.hibernate.reddeer.criteriaeditor,
> 26: org.jboss.tools.hibernate.reddeer.ui.xml.editor,
> 27: org.jboss.tools.hibernate.reddeer.console.views,
> 28: org.jboss.tools.hibernate.reddeer.hqleditor,
> 29: org.jboss.tools.hibernate.reddeer.mapper.editors,
> 30: org.jboss.tools.hibernate.reddeer.jdt.ui.wizards,
> 31: org.jboss.tools.hibernate.reddeer.codegen,
> 32: org.jboss.tools.hibernate.reddeer.jdt.ui.jpa.process.wizard,
> 33: org.jboss.tools.hibernate.reddeer.jpt.ui.wizard
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24340) CDK3 tools works behind proxy - Test case
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24340?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-24340.
---------------------------------
> CDK3 tools works behind proxy - Test case
> -----------------------------------------
>
> Key: JBIDE-24340
> URL: https://issues.jboss.org/browse/JBIDE-24340
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdk, docker, integration-tests, openshift
> Affects Versions: 4.4.4.Final
> Environment: Linux (Fedora), Mac OS, Windows
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Fix For: 4.5.1.AM1
>
> Attachments: create_proxy-test_env.sh
>
>
> It is still impossible to test CDK 3 on central-ci and so, it is willing to test CDK 3 tools operated from devstudio via usage of proxy system settings on local machines.
> Steps to follow:
> 1. Setup local firewall/network rules to simulate that machine resides in restricted network and requires proxy to utilize CDK3 features. ( [^create_proxy-test_env.sh] )
> 2. Download/install devstudio
> 3. Download CDK3 minishift binary and prepare the environemnt (run minishift setup-cdk)
> 4. ASSERT: Cannot subscribe minishift-rhel image during minishift start, can be done via cli
> 4. Set env. variable MINISHIFT_HTTP(S)_PROXY
> 5. Start devstudio, add new Container Development Environement server
> 6. Start server adapter
> 7. ASSERT: CDK tools are working properly - CDK started successfully
> * rhel-image was subscribed
> * docker image pulled
> * log into openshift
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months