[jbosstools-issues] [JBoss JIRA] (JBIDE-13817) aggregate site build should produce junit test output to confirm if the contents of the zips fetched from the upstream composite site match 100% the contents of the produced aggregate site

[Nick Boldt (JIRA)]

Nick Boldt created JBIDE-13817:
----------------------------------

             Summary: aggregate site build should produce junit test output to confirm if the contents of the zips fetched from the upstream composite site match 100% the contents of the produced aggregate site
                 Key: JBIDE-13817
                 URL: https://issues.jboss.org/browse/JBIDE-13817
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: Build/Releng, updatesite
    Affects Versions: 4.1.0.Alpha1
            Reporter: Nick Boldt
            Assignee: Mickael Istria
             Fix For: 4.1.0.Alpha2


The old way to pull zips is with build-sites/aggregate/build.xml. It is an incomplete solution.

The new way should be an *optional* mojo (runs only for aggregate builds, not individual project builds) which:

* reads the upstream composite site [1], and 
** for each child site listed,
*** downloads a zip matching the last CI build for that project
**** IFF the contents of that downloaded zip match the IU versions of the aggregate site we just built, then produce a passing JUnit xml report. If the contents differ, return an error report.

Aggregate jobs will therefore need to be updated to look for these JUnit reports, and mark the build UNSTABLE (yellow) if any non-passing results are found.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira