[jbosstools-issues] [JBoss JIRA] (JBIDE-11096) setup test runs that use p2director to verify update site install

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-11096:
------------------------------------

Another approach, using groovy to launch p2.director:

http://svn.jboss.org/repos/devstudio/trunk/qa/install-extras/build.xml
                
> setup test runs that use p2director to verify update site install
> -----------------------------------------------------------------
>
>                 Key: JBIDE-11096
>                 URL: https://issues.jboss.org/browse/JBIDE-11096
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng
>            Reporter: Max Rydahl Andersen
>            Assignee: Nick Boldt
>             Fix For: 3.3.0.Beta2
>
>
> idea is to have a separate hudson job that runs p2director for each top level feature/category.
> See https://www.jboss.org/tools/download/installation/update_3_3#fromscript for sample code
> Generate junit.xml which has a failure/success for:
> * WHOLE SITE
> * Abridged and other individual categories
> * each single feature
> * each source feature
> Should run first against the aggregate site ZIP, then the aggregate site (exploded).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira