[JBoss JIRA] (JBIDE-22134) Sometimes docker image data are not shown in Deploy to OpenShift wizard
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22134?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-22134:
---------------------------------------
[~mlabuda] "... I am not sure at the moment what is causing it, but when deploying a local docker image (image already pulled) to OpenShift, environment variables and exposed ports are empty, even though when using an image which has not been pulled yet.." is confusing to me. I don't fully understand what you are trying to express here.
Do we know for certain the docker metadata expresses env vars and ports? If those items were not declared in the Dockerfile when the image was built, they will not appear in the metadata. You can verify with 'docker inspect IMAGENAME'
> Sometimes docker image data are not shown in Deploy to OpenShift wizard
> -----------------------------------------------------------------------
>
> Key: JBIDE-22134
> URL: https://issues.jboss.org/browse/JBIDE-22134
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
>
> Sometimes docker image data are not shown/processed in Deploy to OpenShift wizard. Environment variables, exposed ports etc. Unfortunately I don't have a way to reproduce it 100 %, I am not sure at the moment what is causing it, but when deploying a local docker image (image already pulled) to OpenShift, environment variables and exposed ports are empty, even though when using an image which has not been pulled yet, I have not spotted this at all.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3710) use brackets logo in icon for Developer Platform installer .exe
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3710?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3710:
------------------------------------
Assignee: Nick Boldt (was: Joshua Wilson)
[~nickboldt] can you take a look at this one? We need to change the default icon for the .exe file to our logo.
> use brackets logo in icon for Developer Platform installer .exe
> ---------------------------------------------------------------
>
> Key: JBDS-3710
> URL: https://issues.jboss.org/browse/JBDS-3710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: RedHatDeveloperStudio_Logo_Installer.ico
>
>
> Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3710) use brackets logo in icon for Developer Platform installer .exe
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3710?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3710:
---------------------------------
Priority: Critical (was: Blocker)
> use brackets logo in icon for Developer Platform installer .exe
> ---------------------------------------------------------------
>
> Key: JBDS-3710
> URL: https://issues.jboss.org/browse/JBDS-3710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Critical
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: RedHatDeveloperStudio_Logo_Installer.ico
>
>
> Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3710) use brackets logo in icon for Developer Platform installer .exe
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3710?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3710:
---------------------------------
Summary: use brackets logo in icon for Developer Platform installer .exe (was: use brackets logo for Developer Platform installer)
> use brackets logo in icon for Developer Platform installer .exe
> ---------------------------------------------------------------
>
> Key: JBDS-3710
> URL: https://issues.jboss.org/browse/JBDS-3710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Max Rydahl Andersen
> Assignee: Joshua Wilson
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: RedHatDeveloperStudio_Logo_Installer.ico
>
>
> Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3782) use brackets logo in UI of Developer Platform installer
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBDS-3782:
------------------------------------
Summary: use brackets logo in UI of Developer Platform installer
Key: JBDS-3782
URL: https://issues.jboss.org/browse/JBDS-3782
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Max Rydahl Andersen
Assignee: Joshua Wilson
Priority: Blocker
Fix For: 9.1.0.GA
Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3627:
------------------------------------
Assignee: Alexey Kazakov (was: Joshua Wilson)
We need to find out what URL we can use in that error message where users can get the info how they can sign T&C.
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Reporter: Joshua Wilson
> Assignee: Alexey Kazakov
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3697) Installed vagrant version in not validated against anything
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3697?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3697:
--------------------------------------
[~jrichter1] could you please provide the steps to reproduce that issue?
> Installed vagrant version in not validated against anything
> -----------------------------------------------------------
>
> Key: JBDS-3697
> URL: https://issues.jboss.org/browse/JBDS-3697
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> It looks like the installer stores the version of a vagrant installation it finds/the user selects, but there is no value it would check it against. (Which is strange because I remember putting it into the code and the html file still references the fields which apparently don't exist anymore).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3697) Installed vagrant version in not validated against anything
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3697?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3697:
---------------------------------
Priority: Major (was: Blocker)
> Installed vagrant version in not validated against anything
> -----------------------------------------------------------
>
> Key: JBDS-3697
> URL: https://issues.jboss.org/browse/JBDS-3697
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> It looks like the installer stores the version of a vagrant installation it finds/the user selects, but there is no value it would check it against. (Which is strange because I remember putting it into the code and the html file still references the fields which apparently don't exist anymore).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years