[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=13372278#comment-13372278 ] 

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

Second job for Integration Stack: [rpm_rh_central_IS_test.weekly|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_rpm_tests/job/rpm_rh_central_IS_test.weekly/]

The script, as it is now written, expects that the update site contains *devstudio-directory.xml*. Hope it isn't problem when I use 
\[1\] https://devstudio.redhat.com/10.0/development/updates/integration-stack/discovery/ *10.1.0.GA/*
instead of 
\[2\] https://devstudio.redhat.com/10.0/development/updates/integration-stack/discovery/

[~nickboldt], please let me know I you want me to rework the script to me able to work with \[1\]. I see that the update site contains compositeContent.xml which is pointing to 10.1.0.GA/ directory which contains devstudio-directory.xml, so I can use compositeContent.xml to fix this problem.

----

I have fixed bug that causes problems during installation of some features. PR \[3\]
\[3\] https://github.com/jbdevstudio/jbdevstudio-qa/pull/130

The list of repositories which p2direct are using during the installation of each RH Central item  consists of $CENTRAL_URL and URL stored in 'siteUrl' attribute (in plugin.jar/plugin xml). Newly the variable in 'siteUrl' if any will be substituted with update site URL delivered from plugin.jar location. So the p2director is now able to find everything they need in proper version.


> 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)