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

[Lukáš Valach (JIRA)]

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

Lukáš Valach commented on JBIDE-23882:
--------------------------------------

PR: https://github.com/jbdevstudio/jbdevstudio-qa/pull/124
Jenkins job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rpm_rh_central_test.weekly/

[~nickboldt], could you please have a look and let me know whether you are satisfied? I have described how it works in job description, you can also review PR, if you want.

Job is currently configured to run from my fork and all parameters predefined, so you can start it as is.

Build #26 passed without errors, because I have used wrong regular expression which I am using for finding of errors in the eclipse log.
Build #27 failed, because I fix that regular expression :) But I have used old RHSCL (alpha 1.1) where is problem with Lucene, so, it correctly detected problem.
{code}
!ENTRY org.eclipse.core.jobs 4 2 2017-02-22 10:11:38.697
!MESSAGE An internal error occurred during: "Repository registry initialization".
!STACK 0
java.lang.ExceptionInInitializerError
	at org.apache.lucene.codecs.lucene40.Lucene40Codec.<init>(Lucene40Codec.java:52)
{code}
Now the build #28 is running, this test should use Devstudio 10.4 and last snapshot of RHSCL. I see that until now one test passed and one failed. I will check it tomorrow.

Do you have any suggestions? Should I run this test only against jbosstools-discovery.earlyaccess_master repository (1) or also against another repositories like (2) and (3)?

(1) https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.earlyaccess_master/latest/all/repo/
(2) https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/<br>
(3) https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.1.0.GA/

Thanks!

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



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