March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24005) Prepare jenkins job for integration of devstudio with cdk3 test

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24005?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-24005: ------------------------------- Story Points: 15 > Prepare jenkins job for integration of devstudio with cdk3 test > --------------------------------------------------------------- > > Key: JBIDE-24005 > URL: https://issues.jboss.org/browse/JBIDE-24005 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.4.4.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk, integration_tests, jenkins > > Automated tests for devstudio server adapter with cdk3 run on jenkins. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24079) baseline check should be bound to package phase

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24079?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24079: ---------------------------------- Assignee: Nick Boldt > baseline check should be bound to package phase > ----------------------------------------------- > > Key: JBIDE-24079 > URL: https://issues.jboss.org/browse/JBIDE-24079 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.AM1, 4.5.0.AM1 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, check > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > The baseline check is currently bound to the verify phase. It would be more convenient to have it bound to the package phase. I think this can be done in the parent POM, not using the default phase -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23882?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23882: ------------------------------------ I believe (unless I'm mistaken) that siteUrl should be pulled from http://download.jboss.org/jbosstools/configuration/ide-config.properties via the jboss.discovery.earlyaccess.site.integration-stack.url or jboss.discovery.site.integration-stack.url value that's active for the current version of devstudio being installed. The hardcoded value in the plugin is probably wrong. Can you confirm this, [~pleacu] ? > Automate test of installation of software from Red Hat Central into devstudio RPM > --------------------------------------------------------------------------------- > > Key: JBIDE-23882 > URL: https://issues.jboss.org/browse/JBIDE-23882 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Environment: RHEL7, devstudio RPM > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.4.4.AM1 > > > We need to catch problems like in JBDS-4263. > [~lvalach] said: {quote} > I think I should automate test of installation from Central, because this procedure is quite time consuming. > {quote} > [~nickboldt] said: {quote} > before you do that might want to look at the existing automated tests we have: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g.... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p.... > of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root > maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally > so ... partial automation > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24079) baseline check should be bound to package phase

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-24079: ---------------------------------- Summary: baseline check should be bound to package phase Key: JBIDE-24079 URL: https://issues.jboss.org/browse/JBIDE-24079 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.4.AM1, 4.5.0.AM1 Reporter: Jeff MAURY Fix For: 4.4.4.AM2, 4.5.0.AM1 The baseline check is currently bound to the verify phase. It would be more convenient to have it bound to the package phase. I think this can be done in the parent POM, not using the default phase -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

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

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-4296?page=com.atlassian.jira.plugin.... ] Pavol Srna updated JBDS-4296: ----------------------------- Story Points: 10 > Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4296 > URL: https://issues.jboss.org/browse/JBDS-4296 > 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: 10.4.0.AM2 > > > We need to create jenkins job which can be used as smoke test for Devstudio installed from installer jar [0], on all three supported OS platforms (RHEL7/Fedora24, Win10, MacOS 10). > 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 devstudio from installer jar > # 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" for example > # Restart Eclipse > # Check for errors > # Should also test if some software from Central works - run quickstarts or wizards > Possible configuration parameters: > * installer jar URL (snapshot/staging/stable) [0] > * 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 [1] for re-running if something fails > [0] https://devstudio.jboss.com/10.0/staging/builds/devstudio-10.3.0.GA-build... or https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_10.0.neon... or https://devstudio.jboss.com/static/10.0/stable/builds/devstudio-10.3.0.GA... > [1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

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

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-4296?page=com.atlassian.jira.plugin.... ] Pavol Srna updated JBDS-4296: ----------------------------- Component/s: integration-tests > Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4296 > URL: https://issues.jboss.org/browse/JBDS-4296 > 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: 10.4.0.AM2 > > > We need to create jenkins job which can be used as smoke test for Devstudio installed from installer jar [0], on all three supported OS platforms (RHEL7/Fedora24, Win10, MacOS 10). > 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 devstudio from installer jar > # 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" for example > # Restart Eclipse > # Check for errors > # Should also test if some software from Central works - run quickstarts or wizards > Possible configuration parameters: > * installer jar URL (snapshot/staging/stable) [0] > * 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 [1] for re-running if something fails > [0] https://devstudio.jboss.com/10.0/staging/builds/devstudio-10.3.0.GA-build... or https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_10.0.neon... or https://devstudio.jboss.com/static/10.0/stable/builds/devstudio-10.3.0.GA... > [1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23882?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23882: ------------------------------- Fix Version/s: 4.4.4.AM1 (was: 4.4.4.AM2) > Automate test of installation of software from Red Hat Central into devstudio RPM > --------------------------------------------------------------------------------- > > Key: JBIDE-23882 > URL: https://issues.jboss.org/browse/JBIDE-23882 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Environment: RHEL7, devstudio RPM > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.4.4.AM1 > > > We need to catch problems like in JBDS-4263. > [~lvalach] said: {quote} > I think I should automate test of installation from Central, because this procedure is quite time consuming. > {quote} > [~nickboldt] said: {quote} > before you do that might want to look at the existing automated tests we have: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g.... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p.... > of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root > maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally > so ... partial automation > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23882?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23882: ------------------------------- Component/s: integration-tests > Automate test of installation of software from Red Hat Central into devstudio RPM > --------------------------------------------------------------------------------- > > Key: JBIDE-23882 > URL: https://issues.jboss.org/browse/JBIDE-23882 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Environment: RHEL7, devstudio RPM > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.4.4.AM2 > > > We need to catch problems like in JBDS-4263. > [~lvalach] said: {quote} > I think I should automate test of installation from Central, because this procedure is quite time consuming. > {quote} > [~nickboldt] said: {quote} > before you do that might want to look at the existing automated tests we have: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g.... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p.... > of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root > maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally > so ... partial automation > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

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

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23726?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23726: ------------------------------- Story Points: 3 > 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: qa > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.4.4.AM2 > > > Automate test JBDS-5893 Priority annotation is supported (CDI1.1+) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

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

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23727?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23727: ------------------------------- Component/s: cdi integration-tests (was: qa) > 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 > Fix For: 4.4.4.AM2 > > > Automate test JBDS-5894 Parameters annotation is supported (CDI1.1+) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 March 2017