[JBoss JIRA] (JBIDE-20714) OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20714?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20714:
--------------------------------
Labels: docker (was: )
> OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20714
> URL: https://issues.jboss.org/browse/JBIDE-20714
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: docker
> Fix For: 4.3.1.Final
>
> Attachments: deploy_image.png
>
>
> Deploying a docker image to a OpenShift 3 server via context menu of a project in tooling is not possible because there is no project listed in the combo labeled "OpenShift Project". See attached screenshot:
> !deploy_image.png!
> If deploying a docker image dialog is opened via context menu of a connection projects are listed here. Issue is only with dialog opened via context menu of a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20721) Add Manage Projects link to Deploy Docker Image dialog
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20721?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20721:
--------------------------------
Labels: docker (was: )
> Add Manage Projects link to Deploy Docker Image dialog
> ------------------------------------------------------
>
> Key: JBIDE-20721
> URL: https://issues.jboss.org/browse/JBIDE-20721
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: docker
> Fix For: 4.3.1.Final
>
>
> If there is no project for a OpenShift 3 connection it is not possible to proceed through Deploy Docker Image dialog opened via context menu of a OpenShift 3 connection. Because combo box for an OpenShift Project is empty and there is no Manage Projects link, one similar to the one in New OpenShift Application wizard.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20125) v3 Import-, application wizard: use easy import, not our custom facility
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20125?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20125:
--------------------------------
Fix Version/s: 4.4.x
(was: 4.3.x)
> v3 Import-, application wizard: use easy import, not our custom facility
> ------------------------------------------------------------------------
>
> Key: JBIDE-20125
> URL: https://issues.jboss.org/browse/JBIDE-20125
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Labels: openshift_v3
> Fix For: 4.4.x
>
>
> The current impl of the import wizard in v2 and v3 is using a custom import logic where it launches m2e for repositories that have a pom.xml and "General project" for all the others. In JBDS-3285 [~mickael_istria] contributed a new Easy import facility for Eclipse that we should use instead of our own minimalistic, custom made approach
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20126) v2 Import-, application wizard: use easy import, not our custom facility
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20126?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20126:
--------------------------------
Fix Version/s: 4.4.x
(was: 4.3.x)
> v2 Import-, application wizard: use easy import, not our custom facility
> ------------------------------------------------------------------------
>
> Key: JBIDE-20126
> URL: https://issues.jboss.org/browse/JBIDE-20126
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Labels: openshift_v2
> Fix For: 4.4.x
>
>
> The current impl of the import wizard in v2 and v3 is using a custom import logic where it launches m2e for repositories that have a pom.xml and "General project" for all the others. In JBDS-3285 [~mickael_istria] contributed a new Easy import facility for Eclipse that we should use instead of our own minimalistic, custom made approach
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20634) Property gear_profile not added to POST when creating an app using Openshift plugin
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20634?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20634:
--------------------------------
Labels: JSON gear openshift_v2 (was: JSON gear openshift v2)
> Property gear_profile not added to POST when creating an app using Openshift plugin
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-20634
> URL: https://issues.jboss.org/browse/JBIDE-20634
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.3.Final
> Environment: Using Openshift Enterprise v2 and JBDS 8.1.0
> Reporter: Samuel Tauil
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: JSON, gear, openshift_v2
> Fix For: 4.3.x
>
>
> When creating a new application using the Openshift plugin and selecting a different gear profile to create the app seems the attribute gear_profile wasn't added properly to the POST http made in the broker. Checking the the same procedure but using the web console the attribute was added properly. This behavior, when creating thru JBDS, forces the app to be created in a different node that was chosen by the user since the attribute is not added to the post JSON.
> This request was generated from JBDS:
> 2015-09-08 17:31:33.396 [INFO ] Started POST "/broker/rest/domain/domain1210/applications?include=cartridges" for 108.212.65.14 at 2015-09-08 17:31:33 -0400 (pid:12413)
> 2015-09-08 17:31:33.400 [INFO ] Processing by ApplicationsController#create as JSON (pid:12413)
> 2015-09-08 17:31:33.400 [INFO ] Parameters: {"name"=>"nanfusecoursetest2", "cartridges"=>[{"name"=>"fuse-1.0.0"}], "include"=>"cartridges", "domain_id"=>"domain1210"} (pid:12413)
> 2015-09-08 17:34:33.950 [INFO ] Started GET "/broker/rest/domain/domain1210" for 108.212.65.14 at 2015-09-08 17:34:33 -0400 (pid:12439)
> 2015-09-08 17:34:33.966 [INFO ] Processing by DomainsController#show as JSON (pid:12439)
> 2015-09-08 17:34:33.966 [INFO ] Parameters: {"id"=>"domain1210"} (pid:12439)
> 2015-09-08 17:34:33.999 [INFO ] Completed 200 OK in 32ms (Views: 6.8ms) (pid:12439)
> This one was generated by the broker web console:
> 2015-09-08 17:22:34.777 [INFO ] Started POST "/broker/rest/domain/domain1210/applications.json" for 127.0.0.1 at 2015-09-08 17:22:34 -0400 (pid:12413)
> 2015-09-08 17:22:34.783 [INFO ] Processing by ApplicationsController#create as JSON (pid:12413)
> 2015-09-08 17:22:34.783 [INFO ] Parameters: {"cartridges"=>["fuse-1.0.0"], "domain_id"=>"domain1210", "gear_profile"=>"fuse_medium", "initial_git_branch"=>"", "initial_git_url"=>"", "name"=>"nanfusecoursetest1"} (pid:12413)
> 2015-09-08 17:24:53.751 [INFO ] Completed 201 Created in 138967ms (Views: 10.9ms) (pid:12413)
> 2015-09-08 17:24:56.599 [INFO ] Started GET "/broker/rest/application/55ef519a7577e6d79a000027.json" for 127.0.0.1 at 2015-09-08 17:24:56 -0400 (pid:12413)
> 2015-09-08 17:24:56.609 [INFO ] Processing by ApplicationsController#show as JSON (pid:12413)
> 2015-09-08 17:24:56.612 [INFO ] Parameters: {"id"=>"55ef519a7577e6d79a000027"} (pid:12413)
> 2015-09-08 17:24:56.679 [INFO ] Completed 200 OK in 66ms (Views: 2.3ms) (pid:12413)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months