[JBoss JIRA] (JBIDE-24125) Import wizard: adapt ITs to changes introduced in JBIDE-24048
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24125?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24125:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Import wizard: adapt ITs to changes introduced in JBIDE-24048
> -------------------------------------------------------------
>
> Key: JBIDE-24125
> URL: https://issues.jboss.org/browse/JBIDE-24125
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Assignee: Jan Novak
> Fix For: 4.5.x
>
>
> In JBIDE-24048 changes have been done to the import wizard. We should change the ITs to cover these changes.
> @rhopp @bdshadow can you please test this since it's a rather larger change and provides changes in how it behaves?
> * Validations were extended:
> ** is the existing clone destination a git repo?
> ** is the existing clone destination a clone of the source that is used in OpenShift?
> * We now also ask the user if he wants to checkout the correct branch (the one that's used in OpenShift) in the existing git repo
> * UI was slightly changed according to requests made in JBIDE-21935
> * We now also close the wizard dialog before executing the import. This should allow the user to continue working.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (JBIDE-23710) Properites: Disable scaling on completed deployments
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23710?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23710:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Properites: Disable scaling on completed deployments
> ----------------------------------------------------
>
> Key: JBIDE-23710
> URL: https://issues.jboss.org/browse/JBIDE-23710
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Radim Hopp
> Labels: openshift_v3, properties
> Fix For: 4.5.x
>
>
> In web console, scaling completed deployments is disabled.
> In devstudio this option is enabled (in Deployments in Properties View) and after scaling up the completed deployment up (from 0 pods), the pods get scaled, but they are immediately scaled down automatically by openshift.
> Sometimes I also got this exception (but not allways):
> {noformat}
> !ENTRY org.jboss.tools.openshift.ui 4 0 2017-01-10 16:32:41.562
> !MESSAGE Unable to scale wildfly-1
> !STACK 0
> com.openshift.restclient.OpenShiftException: Exception trying to PUT https://10.40.4.205:8443/api/v1/namespaces/testproject/replicationcontrol... response code: 409 Operation cannot be fulfilled on replicationcontrollers "wildfly-1": the object has been modified; please apply your changes to the latest version and try again
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
> at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
> at okhttp3.RealCall.execute(RealCall.java:57)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183)
> at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:275)
> at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler$2.run(ScaleDeploymentHandler.java:183)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> I think we should do the same as web console -> disable scaling options on completed deployments.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (JBIDE-20730) Displaying of a project in OpenShift Explorer view is not consistent
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20730?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20730:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Displaying of a project in OpenShift Explorer view is not consistent
> --------------------------------------------------------------------
>
> Key: JBIDE-20730
> URL: https://issues.jboss.org/browse/JBIDE-20730
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Labels: explorer, openshift_v3
> Fix For: 4.5.x
>
>
> OpenShift 3 project is displayed a bit tricky in OpenShift Explorer view. If project has only project name, then project name is shown as normal text in OpenShift Explorer view under an OpenShift 3 connection. But if a project has set also an optional attribute displayName, then this name is used as a normal text under an OpenShift 3 connection and it's name is used only as a decorated text in parenthesis. Example:
> Project 01 has name: project01
> Project 02 has name: project02 and displayName: projectName02
> In OpenShift Explorer view are those projects shown as
> project01
> projectName02 (project02)
> One could think that project01 and projectName02 are the same attribute of a project, but it's not. I think we could and should show projects like this:
> project01 (project01)
> projectName02 (project02)
> because default value for a displayName is attribute name. In that case it would be consistent and user would not be confused.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months