May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23726) Automate test JBDS-5893 Priority annotation is supported (CDI1.1+)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23726?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-23726: --------------------------------- Priority: Minor (was: Major) > Automate test JBDS-5893 Priority annotation is supported (CDI1.1+) > ------------------------------------------------------------------ > > Key: JBIDE-23726 > URL: https://issues.jboss.org/browse/JBIDE-23726 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi, integration-tests > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Priority: Minor > Fix For: 4.5.0.AM2 > > > Automate test JBDS-5893 Priority annotation is supported (CDI1.1+) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23727) Automate test JBDS-5894 Parameters annotation is supported (CDI1.1+)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23727?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-23727: --------------------------------- Priority: Minor (was: Major) > Automate test JBDS-5894 Parameters annotation is supported (CDI1.1+) > -------------------------------------------------------------------- > > Key: JBIDE-23727 > URL: https://issues.jboss.org/browse/JBIDE-23727 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi, integration-tests > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Priority: Minor > Fix For: 4.5.0.AM2 > > > Automate test JBDS-5894 Parameters annotation is supported (CDI1.1+) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23725) Automate test JBDS-5892 Bean discovery in explicit and implicit archives is supported (CDI1.1+)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23725?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-23725: --------------------------------- Priority: Minor (was: Major) > Automate test JBDS-5892 Bean discovery in explicit and implicit archives is supported (CDI1.1+) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23725 > URL: https://issues.jboss.org/browse/JBIDE-23725 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi, integration-tests > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Priority: Minor > Fix For: 4.5.0.AM2 > > > Automate test JBDS-5892 Bean discovery in explicit and implicit archives is supported (CDI1.1+) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24499) Deploy Docker Image wizard: no projects are available if connection wasn't expanded in explorer

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24499: ---------------------------------------- Summary: Deploy Docker Image wizard: no projects are available if connection wasn't expanded in explorer Key: JBIDE-24499 URL: https://issues.jboss.org/browse/JBIDE-24499 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.4.Final Reporter: Andre Dietisheim Attachments: image-2017-05-23-11-20-07-473.png -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24498) Deploy Docker Image wizard: results dialog is not very informative

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24498?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24498: ------------------------------------- Labels: deploy_docker_wizard openshift_v3 (was: ) > Deploy Docker Image wizard: results dialog is not very informative > ------------------------------------------------------------------ > > Key: JBIDE-24498 > URL: https://issues.jboss.org/browse/JBIDE-24498 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Attachments: image-2017-05-23-11-07-21-461.png > > > steps to reproduce: > # ASSERT: have a docker connection > # ASSERT: have an OpenShift connection > # EXEC: in "Docker Explorer": select an image and pick "Deploy to OpenShift..." > # ASSERT: deploy docker image wizard pops up > # EXEC: provide settings and finish the wizard > Result: > A dialog pops up informing you about the result of your deployment. > !image-2017-05-23-11-07-21-461.png! > But the dialog is not very informative, it's far from obvious what the different informations are all about: > * If there's an error deploying (ex. you have chosen to "Push to the registry" but the registry is not reachable from the local docker daemon that holds the image that you want to deploy) the error is displayed in the title area. It's not visible at first sight that it's an error. Only by reading you're discovering it. (ex. add an error decorator) > * There's a list of items. Nothing in the dialog tells the user what these items are. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24498) Deploy Docker Image wizard: results dialog is not very informative

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24498: ---------------------------------------- Summary: Deploy Docker Image wizard: results dialog is not very informative Key: JBIDE-24498 URL: https://issues.jboss.org/browse/JBIDE-24498 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.4.Final Reporter: Andre Dietisheim Attachments: image-2017-05-23-11-07-21-461.png steps to reproduce: # ASSERT: have a docker connection # ASSERT: have an OpenShift connection # EXEC: in "Docker Explorer": select an image and pick "Deploy to OpenShift..." # ASSERT: deploy docker image wizard pops up # EXEC: provide settings and finish the wizard Result: A dialog pops up informing you about the result of your deployment. !image-2017-05-23-11-07-21-461.png! But the dialog is not very informative, it's far from obvious what the different informations are all about: * If there's an error deploying (ex. you have chosen to "Push to the registry" but the registry is not reachable from the local docker daemon that holds the image that you want to deploy) the error is displayed in the title area. It's not visible at first sight that it's an error. Only by reading you're discovering it. (ex. add an error decorator) * There's a list of items. Nothing in the dialog tells the user what these items are. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24497) Improve devstudio-ui-central test to make it able to deal with remediation page

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24497?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-24497: --------------------------------- Story Points: 6 > Improve devstudio-ui-central test to make it able to deal with remediation page > ------------------------------------------------------------------------------- > > Key: JBIDE-24497 > URL: https://issues.jboss.org/browse/JBIDE-24497 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.5.0.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.0.AM1 > > > Devstudio-ui-central \[1\] test installs all the stuff from RH Central. It may happen that a remediation page appear during the installation. > We need to improve test to make it able to catch/report and deal with remediation page. > \[1\] https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/devstudio-ui-ce... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24497) Improve devstudio-ui-central test to make it able to deal with remediation page

by Lukáš Valach (JIRA)

Lukáš Valach created JBIDE-24497: ------------------------------------ Summary: Improve devstudio-ui-central test to make it able to deal with remediation page Key: JBIDE-24497 URL: https://issues.jboss.org/browse/JBIDE-24497 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests, qa Affects Versions: 4.5.0.AM1 Reporter: Lukáš Valach Assignee: Lukáš Valach Fix For: 4.5.0.AM1 Devstudio-ui-central \[1\] test installs all the stuff from RH Central. It may happen that a remediation page appear during the installation. We need to improve test to make it able to catch/report and deal with remediation page. \[1\] https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/devstudio-ui-ce... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4295) Create smoke test that installs Devstudio RPM and then all the Central/EarlyAccess stuff on top

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4295?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4295: ------------------------------------ We are still not able to run tests using mvn clean verify -Dtest.installBase=path/to/devstudio/rpm but I have implemented this test using workaround (described in JBIDE-23489). Job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... PR: https://github.com/jbdevstudio/jbdevstudio-qa/pull/136 Will do some changes to enable modification of RPM source (to be able to switch between stable/staging/snapshot), see JBIDE-24496. > Create smoke test that installs Devstudio RPM and then all the Central/EarlyAccess stuff on top > ----------------------------------------------------------------------------------------------- > > Key: JBDS-4295 > URL: https://issues.jboss.org/browse/JBDS-4295 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: integration-tests, rpm > Affects Versions: 10.4.0.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 11.0.0.AM1 > > > We need to create jenkins job which can be used as smoke test for Devstudio installed from RPM on RHEL7 via the RHSCL yum repo [1] & the devstudio yum repo [2]. This job should be configurable, we want to be able to pass in a different parameters as URLs and then use the same job to test both snapshot and staging. > The job should: > # Install rh-eclipse46-devstudio > # Clean and start eclipse in strict mode and in clean work space > # Install all stuff from Red Hat Central *using graphical interface* > ** Install everything at once - this is the fastest approach but also makes diagnosing errors more difficult. > ** So, when problems occur, could re-run the job (manually or with naginator plugin?) using parameter connectorIDsToInstall = "net.sourceforge.pmd.eclipse" [3] for example > # Restart Eclipse > # Check for errors > # Should also test if some software from Central works - run quickstarts or wizards > Possible configuration parameters: > * RPM URL (snapshot/staging/stable) [2] > * RHSCL URL[1] > * jboss.discovery.directory.url, jboss.discovery.site.integration-stack.url or something similar (eg., https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... or https://devstudio.redhat.com/10.0/staging/updates/discovery.earlyaccess/1... or https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/) > * ERROR_PATTERN (like [rpm_rh_central_test|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.red...] has) > * TESTS_FORK = jbosstools ? > * TEST_BRANCH = master or jbosstools-4.4.x or jbosstools-4.4.4.x ? > * connectorIDsToInstall = "" (install everything found) or specific value [3] for re-running if something fails > [1] http://download.devel.redhat.com/rel-eng/latest-RHSCL-2-RHEL-7/compose/Se... or similar > [2] https://devstudio.jboss.com/static/10.0/stable/rpms/x86_64/ or https://devstudio.jboss.com/10.0/staging/builds/devstudio-10.3.0.GA-build... or https://devstudio.jboss.com/10.0/snapshots/rpms/10.4.0/x86_64/ > [3] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24496) Enable RPM tests to switch source between stable/staging/snapshot

by Lukáš Valach (JIRA)

Lukáš Valach created JBIDE-24496: ------------------------------------ Summary: Enable RPM tests to switch source between stable/staging/snapshot Key: JBIDE-24496 URL: https://issues.jboss.org/browse/JBIDE-24496 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests, rpm Affects Versions: 4.5.0.AM1 Reporter: Lukáš Valach Assignee: Lukáš Valach Fix For: 4.5.0.AM1 We have some RPM tests \[1\] which install Devstudio from snapshot repository, we need to be able to choose RPM source. This requirement is stated in JBDS-4295 but this feature can be usefull in all tests. \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 May 2017