[JBoss JIRA] (JBDS-4030) Can't use Vagrant 1.7.4 with installer
by Jeff MAURY (JIRA)
Jeff MAURY created JBDS-4030:
--------------------------------
Summary: Can't use Vagrant 1.7.4 with installer
Key: JBDS-4030
URL: https://issues.jboss.org/browse/JBDS-4030
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: platform-installer
Affects Versions: 10.1.0.AM3
Reporter: Jeff MAURY
The installer claims Vagrant minimum is 1.7.4. I have this but installer refuses to continue
I'm using devsuite-1.1.0-GA-20160831-126-installer.exe
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (JBDS-3811) Register/forgot login links don't respond when login form is empty and no error message is present yet
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3811?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3811:
-------------------------------------
[~jrichter1], I'd say it is UI issue. Input fields should not jump back and forth to show validation messages JBDS-4029. I could not replicate because I was clicking Register link after messages got visible.
> Register/forgot login links don't respond when login form is empty and no error message is present yet
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3811
> URL: https://issues.jboss.org/browse/JBDS-3811
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc, ui
>
> Open the installer -> focus is on the username field.
> Click one of the links below the form -> the error message saying the form is empty appears, but the web page doesn't open. You have to click a second time for it to respond.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (JBIDE-23026) Integration tests: improve test stability
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23026?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23026:
-------------------------------------
Fix Version/s: 4.4.x
(was: 4.5.x)
> Integration tests: improve test stability
> -----------------------------------------
>
> Key: JBIDE-23026
> URL: https://issues.jboss.org/browse/JBIDE-23026
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.x
>
>
> There are several impediments to the test stability:
> * tests dont set up their env individually
> * some tests assert the oc binary, but this binary is not the same across platforms (oc, oc.exe, etc): org.jboss.tools.openshift.reddeer.requirement.OCBinary et org.jboss.tools.openshift.reddeer.utils.OpenShiftLabel
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
by Lalatendu Mohanty (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ]
Lalatendu Mohanty commented on JBIDE-23016:
-------------------------------------------
I think the last resort would be to ask user to do "vagrant up" manually for first time in a terminal.
> When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23016
> URL: https://issues.jboss.org/browse/JBIDE-23016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.1.Final
>
>
> The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already).
> This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights.
> When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
by Lalatendu Mohanty (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ]
Lalatendu Mohanty commented on JBIDE-23016:
-------------------------------------------
We can also try to do the steps which Landrush does as part of Vagrant up as part of DevStudio. So when "vagrant up" is done we will not ask for sudoers username/password.
> When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23016
> URL: https://issues.jboss.org/browse/JBIDE-23016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.1.Final
>
>
> The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already).
> This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights.
> When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months