December 2013 - jbosstools-issues

[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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10435?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10435: ------------------------------------- Estimated Difficulty: Medium > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13299) Server Adapter Editor: should notice if project is removed/recreated

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13299?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13299: ------------------------------------- Assignee: (was: Rob Stryker) > Server Adapter Editor: should notice if project is removed/recreated > -------------------------------------------------------------------- > > Key: JBIDE-13299 > URL: https://issues.jboss.org/browse/JBIDE-13299 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Fix For: LATER > > > The server adapter editor should notice if it's deploy project is removed/recreated > How to reproduce: > # EXEC: launch *OpenShift Application* wizard and create some application > # ASSERT: the applicaiton is imported into a project in your workspace and the server adapter for it is created > # EXEC: open the server adapter editor > # ASSERT: *Deploy Project* combo is enabled and shows the workspace project > # EXEC: delete the project from your workspace > Result: > *Deploy project* is still selected even though the project was deleted. It should live react to this removal, remove the project from the combo. > Workaround: > Close and reopen the server adapter editor. > (btw. the server adapter will inform you when you try to use it to publish. It'll tell you that the project it is bound to is not existing any more) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10067) Provide capability to signup to openshift in openshift client

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10067?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10067: ------------------------------------- Assignee: (was: Andre Dietisheim) > Provide capability to signup to openshift in openshift client > ------------------------------------------------------------- > > Key: JBIDE-10067 > URL: https://issues.jboss.org/browse/JBIDE-10067 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.M4 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: LATER > > > We currently dont offer the possibility to signup to the OpenShift Express PaaS. We only offer a link to the signup page on OpenShift. The REST service now offers this capability and it's now up to us to include this into our client. > There are implementation details to discuss with the OpenShift Express team, since they currently offer this capability only with a shared secret (see Appcelerator and mails discussing this topic). As opensource project it's not possible for us to require a shared secret we have to hide from the public. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13299) Server Adapter Editor: should notice if project is removed/recreated

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13299?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13299: ------------------------------------- Estimated Difficulty: Medium > Server Adapter Editor: should notice if project is removed/recreated > -------------------------------------------------------------------- > > Key: JBIDE-13299 > URL: https://issues.jboss.org/browse/JBIDE-13299 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Fix For: LATER > > > The server adapter editor should notice if it's deploy project is removed/recreated > How to reproduce: > # EXEC: launch *OpenShift Application* wizard and create some application > # ASSERT: the applicaiton is imported into a project in your workspace and the server adapter for it is created > # EXEC: open the server adapter editor > # ASSERT: *Deploy Project* combo is enabled and shows the workspace project > # EXEC: delete the project from your workspace > Result: > *Deploy project* is still selected even though the project was deleted. It should live react to this removal, remove the project from the combo. > Workaround: > Close and reopen the server adapter editor. > (btw. the server adapter will inform you when you try to use it to publish. It'll tell you that the project it is bound to is not existing any more) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10067) Provide capability to signup to openshift in openshift client

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10067?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10067: ------------------------------------- Estimated Difficulty: Medium > Provide capability to signup to openshift in openshift client > ------------------------------------------------------------- > > Key: JBIDE-10067 > URL: https://issues.jboss.org/browse/JBIDE-10067 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.M4 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: LATER > > > We currently dont offer the possibility to signup to the OpenShift Express PaaS. We only offer a link to the signup page on OpenShift. The REST service now offers this capability and it's now up to us to include this into our client. > There are implementation details to discuss with the OpenShift Express team, since they currently offer this capability only with a shared secret (see Appcelerator and mails discussing this topic). As opensource project it's not possible for us to require a shared secret we have to hide from the public. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13193) Allow git operations over https instead of ssh

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13193?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13193: ------------------------------------- Estimated Difficulty: Medium > Allow git operations over https instead of ssh > ---------------------------------------------- > > Key: JBIDE-13193 > URL: https://issues.jboss.org/browse/JBIDE-13193 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Xavier Coulon > Fix For: LATER > > > If the user has some required proxy settings, he may need to tweek his git global config to be able run clone/push/pull git operations. > Furthermore, in some corporate environments, proxies may not allow for ssh usage . > The OpenShift tooling could offer an alternative by switching to https instead of ssh protocol, provided that openshift.com itself supports the former one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12016?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12016: ------------------------------------- Labels: application_wizard (was: ) > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13193) Allow git operations over https instead of ssh

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13193?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13193: ------------------------------------- Assignee: (was: Andre Dietisheim) > Allow git operations over https instead of ssh > ---------------------------------------------- > > Key: JBIDE-13193 > URL: https://issues.jboss.org/browse/JBIDE-13193 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Xavier Coulon > Fix For: LATER > > > If the user has some required proxy settings, he may need to tweek his git global config to be able run clone/push/pull git operations. > Furthermore, in some corporate environments, proxies may not allow for ssh usage . > The OpenShift tooling could offer an alternative by switching to https instead of ssh protocol, provided that openshift.com itself supports the former one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12016?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12016: ------------------------------------- Summary: Application wizard: OpenShift Wizard should warn if there are no private keys on local machine that match the public keys on OpenShift (was: OpenShift Wizard should warn if there are no private keys on local machine that match the public keys on OpenShift ) > 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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16157) Typo in OpenShift preferences: time out > timeout

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16157?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16157: ------------------------------------- Estimated Difficulty: Low > Typo in OpenShift preferences: time out > timeout > ------------------------------------------------- > > Key: JBIDE-16157 > URL: https://issues.jboss.org/browse/JBIDE-16157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1, 4.2.0.Alpha1 > Reporter: Michelle Murray > Fix For: 4.2.x > > > In JBIDE-16044 (+ JBIDE-16051), I stated that the field name in the OpenShift pane of Preferences window should be 'Request remote time out'. > I was wrong. It should be one word in this instance. So 'Request remote *timeout*'. > FYI, both one word and two word usages exist but for use in different instances: > * time out = verb, e.g. the server will time out > * timeout = adjective or noun, e.g. timeout behavior or server timeout -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2013