[ 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 -- This message was sent by Atlassian JIRA (v7.2.3#72005)