[JBoss JIRA] (JBIDE-22999) Red Hat Central Rebranding
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22999?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-22999 at 1/23/17 6:13 PM:
--------------------------------------------------------------
I used a light color (#eee) for the cog, which gives a -somewhat- similar look to the tools_rebrand_r2v1.png mockup
!redhat-central-rebranded.png|width=700!
was (Author: fbricon):
I used a light color (#eee) for the cog, which give a similar look to the tools_rebrand_r2v1.png mockup
!redhat-central-rebranded.png|width=700!
> Red Hat Central Rebranding
> --------------------------
>
> Key: JBIDE-22999
> URL: https://issues.jboss.org/browse/JBIDE-22999
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Labels: new_and_noteworthy
> Fix For: 4.4.3.AM2
>
> Attachments: central-rhd-icon.png, fullIDE.png, jbosstools-central-webpage-2.0.0-revised.zip, redhat-central-rebranded.png, tools_rebrand.png, tools_rebrand_r1v2.png, tools_rebrand_r1v3.png, tools_rebrand_r2v1.png
>
>
> Quoting [~james.cobb], from JBIDE-22382
> {quote}
> I've pulled in the branding fro RHD into this IDE panel.
> 1. I've opted to use colors verses an grey monotones
> 2. I've used Red Hat icons from the icon set
> Thoughts?
> {quote}
> !tools_rebrand.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22999) Red Hat Central Rebranding
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22999?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22999:
--------------------------------
Labels: new_and_noteworthy (was: )
> Red Hat Central Rebranding
> --------------------------
>
> Key: JBIDE-22999
> URL: https://issues.jboss.org/browse/JBIDE-22999
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Labels: new_and_noteworthy
> Fix For: 4.4.3.AM2
>
> Attachments: central-rhd-icon.png, fullIDE.png, jbosstools-central-webpage-2.0.0-revised.zip, redhat-central-rebranded.png, tools_rebrand.png, tools_rebrand_r1v2.png, tools_rebrand_r1v3.png, tools_rebrand_r2v1.png
>
>
> Quoting [~james.cobb], from JBIDE-22382
> {quote}
> I've pulled in the branding fro RHD into this IDE panel.
> 1. I've opted to use colors verses an grey monotones
> 2. I've used Red Hat icons from the icon set
> Thoughts?
> {quote}
> !tools_rebrand.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22999) Red Hat Central Rebranding
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22999?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22999:
--------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.x)
> Red Hat Central Rebranding
> --------------------------
>
> Key: JBIDE-22999
> URL: https://issues.jboss.org/browse/JBIDE-22999
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Fix For: 4.4.3.AM2
>
> Attachments: central-rhd-icon.png, fullIDE.png, jbosstools-central-webpage-2.0.0-revised.zip, redhat-central-rebranded.png, tools_rebrand.png, tools_rebrand_r1v2.png, tools_rebrand_r1v3.png, tools_rebrand_r2v1.png
>
>
> Quoting [~james.cobb], from JBIDE-22382
> {quote}
> I've pulled in the branding fro RHD into this IDE panel.
> 1. I've opted to use colors verses an grey monotones
> 2. I've used Red Hat icons from the icon set
> Thoughts?
> {quote}
> !tools_rebrand.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22999) Red Hat Central Rebranding
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22999?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-22999 at 1/23/17 6:02 PM:
--------------------------------------------------------------
I used a light color (#eee) for the cog, which give a similar look to the tools_rebrand_r2v1.png mockup
!redhat-central-rebranded.png|width=700!
was (Author: fbricon):
I used a light color (#eee) for the cog, which give a similar look to the tools_rebrand_r2v1.png mockup
!redhat-central-rebranded.png!
> Red Hat Central Rebranding
> --------------------------
>
> Key: JBIDE-22999
> URL: https://issues.jboss.org/browse/JBIDE-22999
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Fix For: 4.4.x
>
> Attachments: central-rhd-icon.png, fullIDE.png, jbosstools-central-webpage-2.0.0-revised.zip, redhat-central-rebranded.png, tools_rebrand.png, tools_rebrand_r1v2.png, tools_rebrand_r1v3.png, tools_rebrand_r2v1.png
>
>
> Quoting [~james.cobb], from JBIDE-22382
> {quote}
> I've pulled in the branding fro RHD into this IDE panel.
> 1. I've opted to use colors verses an grey monotones
> 2. I've used Red Hat icons from the icon set
> Thoughts?
> {quote}
> !tools_rebrand.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22999) Red Hat Central Rebranding
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22999?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22999:
-------------------------------------
I used a light color (#eee) for the cog, which give a similar look to the tools_rebrand_r2v1.png mockup
!redhat-central-rebranded.png!
> Red Hat Central Rebranding
> --------------------------
>
> Key: JBIDE-22999
> URL: https://issues.jboss.org/browse/JBIDE-22999
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Fix For: 4.4.x
>
> Attachments: central-rhd-icon.png, fullIDE.png, jbosstools-central-webpage-2.0.0-revised.zip, redhat-central-rebranded.png, tools_rebrand.png, tools_rebrand_r1v2.png, tools_rebrand_r1v3.png, tools_rebrand_r2v1.png
>
>
> Quoting [~james.cobb], from JBIDE-22382
> {quote}
> I've pulled in the branding fro RHD into this IDE panel.
> 1. I've opted to use colors verses an grey monotones
> 2. I've used Red Hat icons from the icon set
> Thoughts?
> {quote}
> !tools_rebrand.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22999) Red Hat Central Rebranding
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22999?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22999:
--------------------------------
Attachment: redhat-central-rebranded.png
> Red Hat Central Rebranding
> --------------------------
>
> Key: JBIDE-22999
> URL: https://issues.jboss.org/browse/JBIDE-22999
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Fix For: 4.4.x
>
> Attachments: central-rhd-icon.png, fullIDE.png, jbosstools-central-webpage-2.0.0-revised.zip, redhat-central-rebranded.png, tools_rebrand.png, tools_rebrand_r1v2.png, tools_rebrand_r1v3.png, tools_rebrand_r2v1.png
>
>
> Quoting [~james.cobb], from JBIDE-22382
> {quote}
> I've pulled in the branding fro RHD into this IDE panel.
> 1. I've opted to use colors verses an grey monotones
> 2. I've used Red Hat icons from the icon set
> Thoughts?
> {quote}
> !tools_rebrand.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4175) NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4175:
----------------------------------
slf4j problem (in Fedora packages, not rh-* packages) appears to be caused by m2e 1.7.1, which embeds slf4j simple 1.7.5 but we have 1.7.4 installed via rh-java-common-slf4j-1.7.4
----
Clean install of SY from the latest http://download.jboss.org/jbosstools/neon/integration/updates/integration... site (updated on Jan 20) ... cannot reproduce the slf4j problem. Seems the dependencies of SY have been updated to remove this extraneous dependency. Could also not reproduce when running the m2e quickstart -- no m2e/slf4j stuff was installed that caused any errors in the log.
---
Updated to rpm 10.3-0.20170121.0921.el7. Installed SY. Launched sample project wizard. No errors.
Installed EVERYTHING from the above site (including Neon.1 stuff) and I get remediation:
{code}
Cannot complete the install because of a conflicting dependency.
Software being installed: Eclipse Help Developer Resources 2.2.0.v20160907-1200 (org.eclipse.help.source.feature.group 2.2.0.v20160907-1200)
Software currently installed: Eclipse Platform 4.6.1.v20160920-1429 (org.eclipse.platform.ide 4.6.1.v20160920-1429)
Only one of the following can be installed at once:
Internet Connection Management 1.3.0.v20160418-1534 (org.eclipse.core.net 1.3.0.v20160418-1534)
Internet Connection Management 1.3.0.v20160920-1429 (org.eclipse.core.net 1.3.0.v20160920-1429)
Cannot satisfy dependency:
From: Eclipse Help System 2.2.0.v20160907-1200 (org.eclipse.help.feature.group 2.2.0.v20160907-1200)
To: org.eclipse.core.net [1.3.0.v20160418-1534]
Cannot satisfy dependency:
From: Eclipse Help Developer Resources 2.2.0.v20160907-1200 (org.eclipse.help.source.feature.group 2.2.0.v20160907-1200)
To: org.eclipse.help.feature.group [2.2.0.v20160907-1200]
Cannot satisfy dependency:
From: Eclipse Platform 4.6.1.v20160920-1429 (org.eclipse.platform.feature.group 4.6.1.v20160920-1429)
To: org.eclipse.core.net [1.3.0.v20160920-1429]
Cannot satisfy dependency:
From: Eclipse Platform 4.6.1.v20160920-1429 (org.eclipse.platform.ide 4.6.1.v20160920-1429)
To: org.eclipse.platform.feature.group [4.6.1.v20160920-1429]{code}
!integration-stack-install-everything-some-deps-are-old-neon.1-versions.png|thumbnail!
!integration-stack-install-everything-some-deps-are-old-neon.1-versions_option2.png|thumbnail!
But this makes sense because the platform already installed is newer than the deps in the site.
---
After installing everything, on restart I get some use constraint violations for these chains:
* javax.annotation-api 1.2.0 / org.eclipse.osgi 3.11.1.v20160920-1429 (org.eclipse.linuxtools.docker.core)
* javax.servlet-api / javax.servlet (org.jboss.tools.browsersim.eclipse, org.jboss.tools.browsersim.ui, org.jboss.tools.cordovasim.eclipse, org.jboss.tools.livereload.core)
This is caused by these new plugins being installed in ~/.eclipse:
* javax.servlet_3.1.0.v201410161800.jar
* edu.umd.cs.findbugs.plugin.eclipse_3.0.1.20150306-5afe4d1 --> exports java.annotation packages: javax.annotation,
javax.annotation.concurrent, javax.annotation.meta
---
After uninstalling all the eclipse-* packages, and reinstalling rh-eclipse46-* packages to update to rh-eclipse46-eclipse-jdt 1:4.6.2-4.2.el7 from rhscl-2.4... I get no more install problems -- I can install all the categorized features.
!install-all-the-categorized-features.png|thumbnail!
There are some uncategorized things that are older versions which can't be installed (because newer already installed) but that should be fine. If a user does this they'll get remediation and may break their install, but it's an easy fix:
* delete ~/.eclipse
* reinstall supported stuff
In future, we should ensure that the Integration Stack doesn't bundle old Neon.1 bits when devstudio / RHSCL is based on Neon.2. But at least everything works.
---
As noted above, I did discover that findbugs re-exports javax.annotations which could cause conflicts w/ docker.core (use constraint violation). So we might have to remove findbugs from Central to avoid this.
> NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Fix For: 10.3.0.AM2
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, devstudio-is-major-feature-groups-to-test.png, install-all-the-categorized-features.png, install-integration-stack-441cr1.png, install-springide383-correctly.png, install-springide383-create-mvc-project-done.png, install-springide383-create-mvc-project.png, integration-stack-install-everything-some-deps-are-old-neon.1-versions.png, integration-stack-install-everything-some-deps-are-old-neon.1-versions_option2.png, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, rh-eclipse46-devstudio10.2.log.20161118-1112_strict.txt, slf4j-error.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, springide382.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
> (copied from comment below to make it sticky)
> Results of installing first half of the items in Central:
> ||Item||Result||Description or Errors||
> |Android_Development_Tools|(/)||
> |JBoss_Hybrid_Mobile_Tools|(/)||
> |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
> |JBoss_Arquillian_Tools|(/)||
> |JBoss_Forge_Tools|(/)||
> |JBoss_OpenShift_2_Tools|(x)|BundleException|
> |JBoss_OpenShift_3_Tools|(x)|BundleException|
> |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Tools_LiveReload|(x)|BundleException|
> |JST_Server|(x)|BundleException|
> |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
> |Atlassian_Connector|(x)|BundleException, loader constraint violation|
> |Eclipse_EGit_Mylyn_Support|(x)|BundleException|
> |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
> |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
> |Eclipse_Checkstyle|(x)|NullPointerException|
> All logs [^JBDS-4175_logs_first_half.tar.gz].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4175) NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4175:
-----------------------------
Attachment: integration-stack-install-everything-some-deps-are-old-neon.1-versions.png
integration-stack-install-everything-some-deps-are-old-neon.1-versions_option2.png
install-all-the-categorized-features.png
> NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Fix For: 10.3.0.AM2
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, devstudio-is-major-feature-groups-to-test.png, install-all-the-categorized-features.png, install-integration-stack-441cr1.png, install-springide383-correctly.png, install-springide383-create-mvc-project-done.png, install-springide383-create-mvc-project.png, integration-stack-install-everything-some-deps-are-old-neon.1-versions.png, integration-stack-install-everything-some-deps-are-old-neon.1-versions_option2.png, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, rh-eclipse46-devstudio10.2.log.20161118-1112_strict.txt, slf4j-error.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, springide382.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
> (copied from comment below to make it sticky)
> Results of installing first half of the items in Central:
> ||Item||Result||Description or Errors||
> |Android_Development_Tools|(/)||
> |JBoss_Hybrid_Mobile_Tools|(/)||
> |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
> |JBoss_Arquillian_Tools|(/)||
> |JBoss_Forge_Tools|(/)||
> |JBoss_OpenShift_2_Tools|(x)|BundleException|
> |JBoss_OpenShift_3_Tools|(x)|BundleException|
> |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Tools_LiveReload|(x)|BundleException|
> |JST_Server|(x)|BundleException|
> |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
> |Atlassian_Connector|(x)|BundleException, loader constraint violation|
> |Eclipse_EGit_Mylyn_Support|(x)|BundleException|
> |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
> |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
> |Eclipse_Checkstyle|(x)|NullPointerException|
> All logs [^JBDS-4175_logs_first_half.tar.gz].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-23136:
---------------------------------------
[~dbocharov] I would be interested in understanding if this docker output you were logged into 172.30.115.181:5000/. I recently learned you can run commands against the docker registry by logging in first using your openshift cluster username and token.
I don't know exactly how our docker push works but I would expect for us to do this properly you would need to be able to access the docker registry and either be able to tag and push to it using the internal IP or have a route. Based on the origin issue ps://github.com/openshift/origin/issues/12603 wouldn't the timeout be an indicator that it is unable to reach the IP? Wouldn't this imply we have an issue in reaching the registry?
> Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23136
> URL: https://issues.jboss.org/browse/JBIDE-23136
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.3.AM2
>
> Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png
>
>
> I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see:
> 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB
> Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411
> Steps to reproduce:
> - have a project with a file named {{Dockerfile}} with the following content (1 line):
> {code}
> FROM fedora:latest
> {code}
> - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}})
> - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}.
> - In the wizard, select the option to push the image to the registry (add a dummy port if needed)
> - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months