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

[Lukáš Valach (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13383489#comment-13383489 ] 

Lukáš Valach commented on JBDS-4296:
------------------------------------

I managed to implement all requirements but I am not sure if is devstudio really started in strict mode and with -clean. I don't know how to verify if these parameters are taking into account. Both will be verified in JBDS-4295 I guess.

Post-install smoke test is started only if both INCLUDED_CONNECTORS and EXCLUDED_CONNECTORS parameters are empty. 

Jenkins job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Devstudio_Installation/job/Post_install_tests/job/Install_sw_from_central/

PR (not merged yet): https://github.com/jbdevstudio/jbdevstudio-qa/pull/132




> Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-4296
>                 URL: https://issues.jboss.org/browse/JBDS-4296
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Task
>          Components: integration-tests, rpm
>    Affects Versions: 10.4.0.AM1
>            Reporter: Lukáš Valach
>            Assignee: Lukáš Valach
>             Fix For: 10.4.0.AM2
>
>
> We need to create jenkins job which can be used as smoke test for Devstudio installed from installer jar [0], on all three supported OS platforms (RHEL7/Fedora24, Win10, MacOS 10). 
> This job should be configurable, we want to be able to pass in a different parameters as URLs and then use the same job to test both snapshot and staging.
> The job should:
> # Install devstudio from installer jar
> # Clean and start eclipse in strict mode and in clean work space
> # Install all stuff from Red Hat Central *using graphical interface*
> ** Install everything at once - this is the fastest approach but also makes diagnosing errors more difficult. 
> ** So, when problems occur, could re-run the job (manually or with naginator plugin?) using parameter connectorIDsToInstall = "net.sourceforge.pmd.eclipse" for example
> # Restart Eclipse
> # Check for errors 
> # Should also test if some software from Central works - run quickstarts or wizards
> Possible configuration parameters:
> * installer jar URL (snapshot/staging/stable) [0]
> * jboss.discovery.directory.url, jboss.discovery.site.integration-stack.url or something similar (eg., https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.earlyaccess_master/latest/all/repo or https://devstudio.redhat.com/10.0/staging/updates/discovery.earlyaccess/10.4.0.AM1/ 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.redhat.com/view/Devstudio/view/devstudio_rpm_tests/job/rpm_rh_central_test.weekly/] 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-product/latest/all/ or https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_10.0.neon/latest/x86_64/ or https://devstudio.jboss.com/static/10.0/stable/builds/devstudio-10.3.0.GA-build-product/latest/all/
> [1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudio/com.jboss.jbds.central.discovery/plugin.xml#L526



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)