[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23490:
------------------------------------------
cherry-picked into jbosstools-4.4.x and bumped openshift.js and openshift.js.feature, there, too
> Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.4.AM1, 4.5.0.AM1
>
> Attachments: ScaledUpPodProblems.webm
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23490:
------------------------------------------
merged PR into master and bumped openshift.js and openshift.js.feature
> Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.4.AM1, 4.5.0.AM1
>
> Attachments: ScaledUpPodProblems.webm
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24043) Upversion jbosstools-server in master and maintenance
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-24043:
-----------------------------------
Summary: Upversion jbosstools-server in master and maintenance
Key: JBIDE-24043
URL: https://issues.jboss.org/browse/JBIDE-24043
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.4.4.AM1, 4.5.0.AM1
Reporter: Rob Stryker
In maintenance:
archives from 3.6.103 to 3.6.104
jmx from 1.8.3 to 1.9.0 bc of API change
wtp from 1.3.103 to 1.3.104
AS from 3.2.3 to 3.2.4
In Master
archives from 3.6.103 to 3.6.110 to leave room in case of emergency
jmx from 1.8.3 to 1.10.0 to leave room and also bc I expect further changes
wtp from 1.3.103 to 1.3.110 to leave room in case of emergency
AS from 3.2.3 to 3.3.0 because I expect API additions and new features
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23709) Properties: Scaling To/Up/Down are missing in context menu when project is selected in explorer
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23709?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23709:
-------------------------------
Fix Version/s: 4.4.4.AM2
(was: 4.5.0.AM1)
> Properties: Scaling To/Up/Down are missing in context menu when project is selected in explorer
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23709
> URL: https://issues.jboss.org/browse/JBIDE-23709
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Fix For: 4.4.4.AM2
>
> Attachments: project-selected-no-scaling.png, service-selected-scaling-possible.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have at least 1 service & pod running in OpenShift
> # EXEC: in OpenShift Explorer: select the project that contains the service/pod
> # EXEC: in Properties view: select "Pod" tab and then your running pod (not the build pod, but the pod that's running your service). Open up the context menu
> Result:
> "Scale" with is child entries is missing from the context menu.
> !project-selected-no-scaling.png!
> While it's present if you have the service selected in the OpenShift Explorer.
> !service-selected-scaling-possible.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23893) [cdk] follow up on changes to cdk3 for marker file
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23893?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23893:
-------------------------------------
The problem here is that the runtime detection API is very much filesystem / folder oriented. You pick a folder and it scans deep, and asks each runtime detector to 'find' a runtime in each folder.
So the driver is the filesystem tree, and then it asks the rt detectors. It doesn't stop when it finds one runtime. It will keep scanning for others. This will become very inefficient if it still tries to scan the entire fs or folder structure of a user's home directory.
But to reverse the logic would be a huge API change.
> [cdk] follow up on changes to cdk3 for marker file
> --------------------------------------------------
>
> Key: JBIDE-23893
> URL: https://issues.jboss.org/browse/JBIDE-23893
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.3.Final
> Reporter: Rob Stryker
> Assignee: Martin Malina
> Fix For: 4.4.4.AM2
>
>
> cdk v3 added marker files with credentials and version information. We need to make use of that.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years