[JBoss JIRA] (JBIDE-25438) Refactor CDK itests to be more stable against CDK starts that fail sometimes
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25438?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25438:
----------------------------------
Description:
Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs.
* repair discovery itests
* finish adding of mocking cdk binaries in unsupported cdk versions
* update suites to run faster test classes
* remove deprecated test cases
* think of skipping registration and adding one test case that will start cdk with registration
* extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations
Issues to be addressed that causes fail of job run:
* CDK-216
* JBIDE-25443
was:
Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs.
* repair discovery itests
* finish adding of mocking cdk binaries in unsupported cdk versions
* update suites to run faster test classes
* remove deprecated test cases
* think of skipping registration and adding one test case that will start cdk with registration
* extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations
Issues to be addressed that causes fail of job run:
* CDK-216
> Refactor CDK itests to be more stable against CDK starts that fail sometimes
> ----------------------------------------------------------------------------
>
> Key: JBIDE-25438
> URL: https://issues.jboss.org/browse/JBIDE-25438
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.5.2.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Fix For: 4.5.2.AM2
>
>
> Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs.
> * repair discovery itests
> * finish adding of mocking cdk binaries in unsupported cdk versions
> * update suites to run faster test classes
> * remove deprecated test cases
> * think of skipping registration and adding one test case that will start cdk with registration
> * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations
> Issues to be addressed that causes fail of job run:
> * CDK-216
> * JBIDE-25443
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25443) CDK itests fail on MAC os slaves with mysterious system warning dialog
by Ondrej Dockal (JIRA)
Ondrej Dockal created JBIDE-25443:
-------------------------------------
Summary: CDK itests fail on MAC os slaves with mysterious system warning dialog
Key: JBIDE-25443
URL: https://issues.jboss.org/browse/JBIDE-25443
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: integration-tests, qa
Affects Versions: 4.5.2.AM2
Environment: MacOS
Reporter: Ondrej Dockal
Assignee: Martin Malina
Priority: Critical
Attachments: image-2017-11-29-12-52-27-497.png
CDK itests are sometimes blocked by system dialog (saying: JBoss Tools Test Applicaiton quit unexpectedly) and causes failures in tests. Also could be just just consequence of crashed test app...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25438) Refactor CDK itests to be more stable against CDK starts that fail sometimes
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25438?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25438:
----------------------------------
Description:
Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs.
* repair discovery itests
* finish adding of mocking cdk binaries in unsupported cdk versions
* update suites to run faster test classes
* remove deprecated test cases
* think of skipping registration and adding one test case that will start cdk with registration
* extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations
Issues to be addressed that causes fail of job run:
* CDK-216
was:
Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs.
* repair discovery itests
* finish adding of mocking cdk binaries in unsupported cdk versions
* update suites to run faster test classes
* remove deprecated test cases
* think of skipping registration and adding one test case that will start cdk with registration
Issues to be addressed that causes fail of job run:
* CDK-216
> Refactor CDK itests to be more stable against CDK starts that fail sometimes
> ----------------------------------------------------------------------------
>
> Key: JBIDE-25438
> URL: https://issues.jboss.org/browse/JBIDE-25438
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.5.2.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Fix For: 4.5.2.AM2
>
>
> Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs.
> * repair discovery itests
> * finish adding of mocking cdk binaries in unsupported cdk versions
> * update suites to run faster test classes
> * remove deprecated test cases
> * think of skipping registration and adding one test case that will start cdk with registration
> * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations
> Issues to be addressed that causes fail of job run:
> * CDK-216
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25442) Add possibility to be notified when user logs in into OSIO
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25442?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova updated JBIDE-25442:
------------------------------------
Labels: OSIO (was: )
> Add possibility to be notified when user logs in into OSIO
> ----------------------------------------------------------
>
> Key: JBIDE-25442
> URL: https://issues.jboss.org/browse/JBIDE-25442
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Lucia Jelinkova
> Labels: OSIO
>
> I have the following scenario I'd like to implement with OSIO login. I am not sure if it is currently possible or it would need some additional implementation.
> The Fabric8 analytics plugin for Eclipse uses LSP server that needs OSIO token to work. The current implementation asks user for the token on the first open of pom.xml file and then every time the LSP server needs to be started (meaning on every open of any pom.xml file). This approach brings some disadvantages - e.g. user might cancel the login window and then he has manually re-enable the server on Fabric8 preference page. Not to mention that the login window out of the nowhere is quite disturbing.
> I would like to change it so that the user logs in into OSIO (via toolbutton or preference page) and then the LSP server is notified about the login and starts working. This would prevent the "login popup" problem and I think it would bring better user experience.
> So, is there a way to get notifications about login/logout into OSIO at the moment? Would you agree to implement this feature into OSIO Eclipse plugin?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25442) Add possibility to be notified when user logs in into OSIO
by Lucia Jelinkova (JIRA)
Lucia Jelinkova created JBIDE-25442:
---------------------------------------
Summary: Add possibility to be notified when user logs in into OSIO
Key: JBIDE-25442
URL: https://issues.jboss.org/browse/JBIDE-25442
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Lucia Jelinkova
I have the following scenario I'd like to implement with OSIO login. I am not sure if it is currently possible or it would need some additional implementation.
The Fabric8 analytics plugin for Eclipse uses LSP server that needs OSIO token to work. The current implementation asks user for the token on the first open of pom.xml file and then every time the LSP server needs to be started (meaning on every open of any pom.xml file). This approach brings some disadvantages - e.g. user might cancel the login window and then he has manually re-enable the server on Fabric8 preference page. Not to mention that the login window out of the nowhere is quite disturbing.
I would like to change it so that the user logs in into OSIO (via toolbutton or preference page) and then the LSP server is notified about the login and starts working. This would prevent the "login popup" problem and I think it would bring better user experience.
So, is there a way to get notifications about login/logout into OSIO at the moment? Would you agree to implement this feature into OSIO Eclipse plugin?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25438) Refactor CDK itests to be more stable against CDK starts that fail sometimes
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25438?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25438:
----------------------------------
Description:
Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs.
* repair discovery itests
* finish adding of mocking cdk binaries in unsupported cdk versions
* update suites to run faster test classes
* remove deprecated test cases
* think of skipping registration and adding one test case that will start cdk with registration
Issues to be addressed that causes fail of job run:
* CDK-216
was:
Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs.
* repair discovery itests
* finish adding of mocking cdk binaries in unsupported cdk versions
* update suites to run faster test classes
* remove deprecated test cases
* think of skipping registration and adding one test case that will start cdk with registration
> Refactor CDK itests to be more stable against CDK starts that fail sometimes
> ----------------------------------------------------------------------------
>
> Key: JBIDE-25438
> URL: https://issues.jboss.org/browse/JBIDE-25438
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.5.2.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Fix For: 4.5.2.AM2
>
>
> Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs.
> * repair discovery itests
> * finish adding of mocking cdk binaries in unsupported cdk versions
> * update suites to run faster test classes
> * remove deprecated test cases
> * think of skipping registration and adding one test case that will start cdk with registration
> Issues to be addressed that causes fail of job run:
> * CDK-216
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBDS-3758) when something goes wrong, give user call to action / report of what went wrong
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3758?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3758.
-----------------------------
> when something goes wrong, give user call to action / report of what went wrong
> -------------------------------------------------------------------------------
>
> Key: JBDS-3758
> URL: https://issues.jboss.org/browse/JBDS-3758
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 11.2.0.AM1
>
> Attachments: jbds-install-ste-failed-progress-bar-keeps-moving.png
>
>
> I attempted to install from Setup-bundled-0.0.2-20160401-33.exe and while the installer was OK with my using my pre-installed JDK 8 in C:\Program Files\Java\jdk1.8.0_25 (or C:\Program Files\Java\jre1.8.0_25) it then ran into a problem using that JDK to install JBDS.
> I noticed the problem at about 12% on the progress bar but it was still moving along at 45% when I grabbed the screenshot (attached).
> If a failure occurs, perhaps *we could change the bar from blue to red and move it to 100%* ?
> Also, should there be a call to action for the user?
> Even something simple like "*go check in C:\DeveloperPlatform\install.log for what might have happened*" would be useful here.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBDS-4583) Allow to maximize the window of the installer
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4583?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4583.
-----------------------------
> Allow to maximize the window of the installer
> ---------------------------------------------
>
> Key: JBDS-4583
> URL: https://issues.jboss.org/browse/JBDS-4583
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Aurélien Pupier
> Fix For: 11.2.0.AM2
>
> Attachments: image-2017-10-10-17-06-22-685.png, image-2017-10-10-17-06-47-629.png, image-2017-10-10-17-07-05-212.png
>
>
> it is particularly useful on "Confirmation" page where selecting the components to install, it will avoid to have a long scrollbar
> currently I ave 3 "dialog size" to see everything:
> !image-2017-10-10-17-06-22-685.png|thumbnail!
> !image-2017-10-10-17-06-47-629.png|thumbnail!
> !image-2017-10-10-17-07-05-212.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBDS-3834) Install fail - what next?
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3834?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3834.
-----------------------------
> Install fail - what next?
> -------------------------
>
> Key: JBDS-3834
> URL: https://issues.jboss.org/browse/JBDS-3834
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Fix For: 11.2.0.AM2
>
> Attachments: error.PNG, fail_install.PNG
>
>
> Testing the Installer a bit more and I realize this is currently tech preview but when one (or more) components fail, there is no next step for users. There is no cancel or quit button to exit the failed install, nor is there a retry for the failed component, nor any error message at all. As a user, I'd be confused about what I should do next at this stage. I think this might be worth looking into with UX for the 9.1 GA++ release.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months