[JBoss JIRA] (JBIDE-21372) Server Adapter: automatically create a server for new apps
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21372?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21372:
-------------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.0.AM1)
> Server Adapter: automatically create a server for new apps
> ----------------------------------------------------------
>
> Key: JBIDE-21372
> URL: https://issues.jboss.org/browse/JBIDE-21372
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.0.Final
>
>
> Currently one has to create the OpenShift 3 server adapter manually by using the menu File > New > Server > OpenShift 3 (or context menu in the Server view). We should now also create the server adapter when one successfully finishes the new/import application wizard. To achieve this we'll have to include a page in the new/import-application wizard for the required server settings.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24307) Filter out Build config which have no git url configured in "Import OpenShift Application" dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24307?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24307:
-------------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.0.AM1)
> Filter out Build config which have no git url configured in "Import OpenShift Application" dialog
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24307
> URL: https://issues.jboss.org/browse/JBIDE-24307
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Aurélien Pupier
> Labels: import_wizard, openshift_v3
> Fix For: 4.5.0.Final
>
> Attachments: image-2017-04-25-15-22-03-598.png, image-2017-04-25-15-22-12-510.png
>
>
> it will avoid to have an error dialog just after
> !image-2017-04-25-15-22-12-510.png|thumbnail!
> Even more that thsi information is already retrieved to be displayed in "Build config details"
> !image-2017-04-25-15-22-03-598.png|thumbnail!
> Anothe rpossibility is to greyet out them with a tooltip explaining why we can't select them
> and/or disabled Next:Finish buttons
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23136:
-------------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.0.AM1)
> 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.5.0.Final
>
> 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)
8 years, 9 months
[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21895:
-------------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.0.AM1)
> Application wizard: Resource name collisions after deleting and recreating the application
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21895
> URL: https://issues.jboss.org/browse/JBIDE-21895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Pavol Srna
> Labels: application_wizard, openshift_v3
> Fix For: 4.5.0.Final
>
> Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png, os-resources-empty.png
>
>
> 1) Create e.g. node application in a openshift project
> 2) Right click from project explorer -> Delete the application
> 3) repeat step 1)
> Result:
> !Screen Shot 2016-03-17 at 16.19.05.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months