[JBoss JIRA] (JBDS-4296) Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4296?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4296:
-----------------------------
Description:
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...
was:
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 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" 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...
> 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: rpm
> Affects Versions: 10.4.0.AM1
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 10.4.0.AM1
>
>
> 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)
8 years, 10 months
[JBoss JIRA] (JBDS-4296) Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4296?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4296:
-----------------------------
Description:
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 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" 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...
was:
We need to create jenkins job which can be used as smoke test for Devstudio installed from installer jar, 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 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" 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)
* 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
[1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools...
> 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: rpm
> Affects Versions: 10.4.0.AM1
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 10.4.0.AM1
>
>
> 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 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" 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)
8 years, 10 months
[JBoss JIRA] (JBDS-4295) Create smoke test that installs Devstudio RPM and then all the Central/EarlyAccess stuff on top
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4295?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4295:
-----------------------------
Description:
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...
was:
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/jbosstools...
> 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: rpm
> Affects Versions: 10.4.0.AM1
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 10.4.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
[JBoss JIRA] (JBDS-4296) Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4296?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4296:
-----------------------------
Description:
We need to create jenkins job which can be used as smoke test for Devstudio installed from installer jar, 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 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" 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)
* 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
[1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools...
was:
We need to create jenkins job which can be used as smoke test for Devstudio installed from installer jar, 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 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" 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)
* RHSCL URL (eg., http://download.devel.redhat.com/rel-eng/latest-RHSCL-2-RHEL-7/compose/Se... )
* 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
[1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools...
> 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: rpm
> Affects Versions: 10.4.0.AM1
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 10.4.0.AM1
>
>
> We need to create jenkins job which can be used as smoke test for Devstudio installed from installer jar, 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 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" 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)
> * 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
> [1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4295) Create smoke test that installs Devstudio RPM and then all the Central/EarlyAccess stuff on top
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4295?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4295:
-----------------------------
Description:
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)
* 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/jbosstools...
was:
We need to create jenkins job which can be used as smoke test for Devstudio installed from RPM. 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" 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)
* RHSCL URL (eg., http://download.devel.redhat.com/rel-eng/latest-RHSCL-2-RHEL-7/compose/Se... )
* 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
[1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools...
> 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: rpm
> Affects Versions: 10.4.0.AM1
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 10.4.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)
> * 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/jbosstools...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4295) Create smoke test that installs Devstudio RPM and then all the Central/EarlyAccess stuff on top
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4295?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4295:
-----------------------------
Description:
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/jbosstools...
was:
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)
* 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/jbosstools...
> 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: rpm
> Affects Versions: 10.4.0.AM1
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 10.4.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/jbosstools...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4296) Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4296?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4296:
-----------------------------
Description:
We need to create jenkins job which can be used as smoke test for Devstudio installed from installer jar, 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 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" 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)
* RHSCL URL (eg., http://download.devel.redhat.com/rel-eng/latest-RHSCL-2-RHEL-7/compose/Se... )
* 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
[1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools...
was:
We need to create jenkins job which can be used as smoke test for Devstudio installed from RPM. 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" 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)
* RHSCL URL (eg., http://download.devel.redhat.com/rel-eng/latest-RHSCL-2-RHEL-7/compose/Se... )
* 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
[1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools...
> 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: rpm
> Affects Versions: 10.4.0.AM1
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 10.4.0.AM1
>
>
> We need to create jenkins job which can be used as smoke test for Devstudio installed from installer jar, 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 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" 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)
> * RHSCL URL (eg., http://download.devel.redhat.com/rel-eng/latest-RHSCL-2-RHEL-7/compose/Se... )
> * 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
> [1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4295) Create smoke test that installs Devstudio RPM and then all the Central/EarlyAccess stuff on top
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4295?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4295:
-----------------------------
Description:
We need to create jenkins job which can be used as smoke test for Devstudio installed from RPM. 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" 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)
* RHSCL URL (eg., http://download.devel.redhat.com/rel-eng/latest-RHSCL-2-RHEL-7/compose/Se... )
* 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
[1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools...
was:
We need to create jenkins job which can be used as smoke test for Devstudio installed from RPM. 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 (?)
# Restart Eclipse
# Check for errors
# Should it also test if some software from Central works? (Use some wizards etc) (?)
# Should it check if central contains a correct number of items(?)
# Any other stuff to do(?)
Possible configuration parameters:
* RPM URL (snapshot/staging/stable)
* RHSCL URL (?)
* jboss.discovery.directory.url, jboss.discovery.site.integration-stack.url or something similar (?)
* ERROR_PATTERN (like [rpm_rh_central_test|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.red...] has)
* TESTS_FORK
* TEST_BRANCH
> 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: rpm
> Affects Versions: 10.4.0.AM1
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 10.4.0.AM1
>
>
> We need to create jenkins job which can be used as smoke test for Devstudio installed from RPM. 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" 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)
> * RHSCL URL (eg., http://download.devel.redhat.com/rel-eng/latest-RHSCL-2-RHEL-7/compose/Se... )
> * 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
> [1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4295) Create smoke test that installs Devstudio RPM and then all the Central/EarlyAccess stuff on top
by Lukáš Valach (JIRA)
Lukáš Valach created JBDS-4295:
----------------------------------
Summary: 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: rpm
Affects Versions: 10.4.0.AM1
Reporter: Lukáš Valach
Assignee: Lukáš Valach
Fix For: 10.4.0.AM1
We need to create jenkins job which can be used as smoke test for Devstudio installed from RPM. 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 (?)
# Restart Eclipse
# Check for errors
# Should it also test if some software from Central works? (Use some wizards etc) (?)
# Should it check if central contains a correct number of items(?)
# Any other stuff to do(?)
Possible configuration parameters:
* RPM URL (snapshot/staging/stable)
* RHSCL URL (?)
* jboss.discovery.directory.url, jboss.discovery.site.integration-stack.url or something similar (?)
* ERROR_PATTERN (like [rpm_rh_central_test|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.red...] has)
* TESTS_FORK
* TEST_BRANCH
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months