[JBoss JIRA] (JBDS-4263) Problems after install from Red Hat Central into rh-eclipse46-devstudio
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4263:
----------------------------------
For testing IS content, we should use the latest released version, which should be linked from the staging and stable sites.
You can find the URLs in this file:
http://download.jboss.org/jbosstools/configuration/ide-config.properties
For the latest devstudio 10.x snapshots, use these:
jboss.discovery.site.integration-stack.url|devstudio|10.4.0.AM1=https://d...
jboss.discovery.earlyaccess.site.integration-stack.url|devstudio|10.4.0.A...
for staging, it'll be:
jboss.discovery.site.integration-stack.url|devstudio|10.4.0.AM1=https://d...
jboss.discovery.earlyaccess.site.integration-stack.url|devstudio|10.4.0.A...
for stable:
jboss.discovery.site.integration-stack.url|devstudio|10=https://devstudio...
jboss.discovery.earlyaccess.site.integration-stack.url|devstudio|10=https...
you should be testing the devstudio 10.4 rpm against the latest available. currently that's the snapshot site. In future we may want to test against the staging site (so a job param would be helpful here so I can trigger the job via script, passing in a different value for the URL or the buildType). That way we can verify the staging site works (during the 3-4 days where we care about that site) and then we can kick the job later to verify that the stable site works too (once we publish staging -> stable).
> Problems after install from Red Hat Central into rh-eclipse46-devstudio
> -----------------------------------------------------------------------
>
> Key: JBDS-4263
> URL: https://issues.jboss.org/browse/JBDS-4263
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.3.0.AM2
> Reporter: Nick Boldt
> Assignee: Lukáš Valach
> Fix For: 10.4.0.AM1
>
> Attachments: build_31_eclipse_log.zip, build_32_eclipse_log.zip, build_33_eclipse_log.zip, home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio-10.4-0.20170227.0853.el7_20170227-0512_install_PMD.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
>
>
> The installation of software from Red Hat Central causes errors in the log. Some functionality may be broken. We have to test installation of all the stuff from the central and fix the problems.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[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)
9 years, 1 month
[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)
9 years, 1 month
[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)
9 years, 1 month
[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)
9 years, 1 month
[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)
9 years, 1 month
[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)
9 years, 1 month
[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)
9 years, 1 month