[JBoss JIRA] (JBIDE-13963) Port-Forwarding: wizard dialog should have "Cancel", "Start" and "Stop" buttons (not "OK" in the bottom & "Start All", "Stop All" to the right of the ports)
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13963?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-13963.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Port-Forwarding: wizard dialog should have "Cancel", "Start" and "Stop" buttons (not "OK" in the bottom & "Start All", "Stop All" to the right of the ports)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13963
> URL: https://issues.jboss.org/browse/JBIDE-13963
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Xavier Coulon
> Priority: Minor
> Labels: port_forwarding_wizard
> Fix For: LATER
>
> Attachments: OpenShift_portforward.png
>
>
> the wizard buttons are a bit misleading: clicking on "Ok" at the bottom of the wizard closes the wizard but does not start or stop the port-forwarding (I got that problem a few times when I was preparing a demo).
> I think the wizard buttons should rather be "Start"/"Cancel" or "Stop/Cancel".
> The "Start all" and "stop all" buttons on the side of the tables should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-12016) Application wizard: OpenShift Wizard should warn if there are no private keys on local machine that match the public keys on OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12016?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-12016.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Application wizard: OpenShift Wizard should warn if there are no private keys on local machine that match the public keys on OpenShift
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12016
> URL: https://issues.jboss.org/browse/JBIDE-12016
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta3, 3.3.0.Final
> Reporter: Burr Sutter
> Priority: Minor
> Labels: application_wizard
> Fix For: LATER
>
> Attachments: cloning-settings.png, creating-domain.png, manage-ssh-keys.png, no-keys.png, Screen Shot 2012-05-25 at 10.57.18 AM.png
>
>
> How to reproduce:
> # ASSERT: make sure you have an account with at least 1 public key on OpenShift
> # ASSERT: make sure you have the private key for this private key registered to your SSH2 preferences in Eclipse
> # EXEC: launch *New OpenShift Application* wizard
> # EXEC: on the last page (git cloning settings), hit the SSH2 Preferences link and remove your private key from the list of private keys
> # ASSERT: back on the git cloning wizard page you're not warned that there's no private key that would match the private keys on your machine
> # EXEC: hit *Finish*
> Result:
> Cloning fails since you have no private key registered to the Eclipse SSH2 preferences that would allow you to clone from OpenShift.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-10435) Application wizard: Warn users if no spare slot for the jenkins builder app (quota full) when enabling jenkins client on application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10435?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-10435.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Application wizard: Warn users if no spare slot for the jenkins builder app (quota full) when enabling jenkins client on application
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-10435
> URL: https://issues.jboss.org/browse/JBIDE-10435
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.M5
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: application_wizard
> Fix For: LATER
>
>
> # ASSERT: make sure that you have only 2 spare application slot (given your quota is 3: have 1 applications) and none of the used apps is a jenkins type app
> # ASSERT: make sure you have a "Dynamic Web Project" in your eclipse workspace
> # EXEC: lauch the OpenShift Application Wizard:embed the jenkins client to it and create the jenkins app for it.
> # EXEC: on the last wizard page: uncheck "Create new", choose your "Dynamic Web Project" and hit "Finish"
> # ASSERT: now you have no spare application slot, quota is full (given qutoa is 3 you now have: 1 pre-existing app, 1 new app, 1 jenkins app)
> # EXEC: log into your jenkins instance and see if your app is building
> Result:
> The jenkins job is waiting for a slave to get available
> The reason is that jenkins needs an additional builder application. You already reached your 3 apps quota and jenkins therefore cannot build your app.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-17554) Properties view: modal progress dialog shows up if properties view displays connection before it was loaded
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17554?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-17554.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Properties view: modal progress dialog shows up if properties view displays connection before it was loaded
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17554
> URL: https://issues.jboss.org/browse/JBIDE-17554
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: properties
> Fix For: LATER
>
> Attachments: loading-connection-details.png
>
>
> Steps to reproduce:
> # ASSERT: make sure you have at least 1 connection and it is not loaded yet (you'd most likely have to freshly start Eclipse since OpenShift cashes its resources)
> # ASSERT: make sure you have properties view opened "hidden" (ex. in the bottom section, opened but not visible)
> # ASSERT: make sure you have OpenShift Explorer visible (ex. in bottom section on top of properties view)
> # EXEC: in OpenShift explorer: select your connection
> # EXEC: switch to Properties view
> Result:
> Some modal dialog with progress shows up while the connection details are loaded
> !loading-connection-details.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-17669) Explorer: Deleted domain after refresh should disappear
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17669?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-17669.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Explorer: Deleted domain after refresh should disappear
> -------------------------------------------------------
>
> Key: JBIDE-17669
> URL: https://issues.jboss.org/browse/JBIDE-17669
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: explorer
> Fix For: LATER
>
>
> While having a domain in OpenShift Explorer in JBT/JBDS and deletion this domain through RHC/web-ui, refresh on it should make it disappear. Instead of it, domain is still presented in the OpenShift explorer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-12118) Port forwarding, Tail files wizard: more specific auth error description
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12118?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-12118.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Port forwarding, Tail files wizard: more specific auth error description
> ------------------------------------------------------------------------
>
> Key: JBIDE-12118
> URL: https://issues.jboss.org/browse/JBIDE-12118
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Stefan Bunciak
> Priority: Minor
> Labels: port_forwarding_wizard
> Fix For: LATER
>
> Attachments: port.png, tail.png
>
>
> Provide a uniform message in the Error dialogs like in JBIDE-11810, saying that user probably doesn't have ssh key listed in preferences.
> Current state:
> * Port forwarding, environment variables
> !port.png|thumbnail!
> * Tail files
> !tail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-13096) SSH key wizard: Add Existing SSH key: automatically provide sensible default-name
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13096?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-13096.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> SSH key wizard: Add Existing SSH key: automatically provide sensible default-name
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-13096
> URL: https://issues.jboss.org/browse/JBIDE-13096
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Beta2
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: sshkeys_wizard
> Fix For: LATER
>
>
> When adding an existing ssh key the user is required to provide a name for the key he's adding (uploading). To the newbie user it is not obvious what he shall provide as name. We should help here a provide some sensible default name.
> How to reproduce:
> # ASSERT: make sure you have an account on OpenShift and in the OpenShift Explorer
> # EXEC: in the OpenShift Explorer: pick "Manage SSH Keys..." from the context-menu of your user
> # EXEC: in the upcoming dialog: hit "Add"
> Result:
> You get a dialog that asks you to browse and select your key and provide a name for it.
> Expected:
> Automatically provide some meaningful default name so that the newbie user may just pick his key and upload.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-12333) Application wizard, Embed wizard: Explicitly provide "Enable jenkins build" (instead of adding jenkins-client cartridge)
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12333?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-12333.
---------------------------------
Resolution: Won't Fix
Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.
> Application wizard, Embed wizard: Explicitly provide "Enable jenkins build" (instead of adding jenkins-client cartridge)
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12333
> URL: https://issues.jboss.org/browse/JBIDE-12333
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: application_wizard, embed_wizard
> Fix For: LATER
>
> Attachments: enable-jenkins-build-2.png, enable-jenkins-build.png
>
>
> If you want to switch to a jenkins based build you'd currently have to add the jenkins-client to your application. The OpenShift WebUI does this in a far more explicit and user friendly way:
> It explicilty features a button that "enable jenkins build"
> !enable-jenkins-build.png!
> !enable-jenkins-build-2.png!
> We should provide something equivalent.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months