[jbosstools-issues] [JBoss JIRA] (JBIDE-16970) create p2diff job to verify that nightly build is different from previous milestone

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-16970 at 12/1/15 11:34 AM:
--------------------------------------------------------------

While we could use p2diff (assuming we can get it to run across all the slaves - in the past it had a tendency to hang, so I removed Mickael's prototype on March 12 2015) [1], we can also just diff the buildinfo.json files to compare the latest list of SHAs in order to determine if there are upstream SOURCE changes, and therefore also BINARY changes.

[1] https://github.com/jbdevstudio/jbdevstudio-ci/commit/ad8371734fb1839bce75076b9f58438828379a65#diff-b63591542f44427ceb7a7f396ac6353dR158

I've added support for diffing ALL the SHAs, not just the first/principal one.

https://github.com/jbosstools/jbosstools-build-ci/commit/cab99f1346fff090d796b8df86ece1e8640dc511?w=1 (4.4.x branch)
https://github.com/jbosstools/jbosstools-build-ci/pull/138 (4.3.x branch)

Local tests indicate this works great - I added a *-debug* flag to make it easier to see why the script is returning "true" (SHAs differ) or "false" (SHAs are unchanged).

So I've added the new *-all* flag to the master job [2] config. Building...

[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-build-sites.aggregate.site_master/ >=11138

If successful I need to:

* push the PR
* rebuild build-ci in 4.3.x branch
* add the *-all* flag to all the aggregate jobs (core, coretests, child sites, integration tests) for both 4.4 and 4.3 branches


was (Author: nickboldt):
While we could use p2diff (assuming we can get it to run across all the slaves - in the past it had a tendency to hang, so I removed Mickael's prototype on March 12 2015) [1], we can also just diff the buildinfo.json files to compare the latest list of SHAs in order to determine if there are upstream SOURCE changes, and therefore also BINARY changes.

[1] https://github.com/jbdevstudio/jbdevstudio-ci/commit/ad8371734fb1839bce75076b9f58438828379a65#diff-b63591542f44427ceb7a7f396ac6353dR158

I've added support for diffing ALL the SHAs, not just the first/principal one.

https://github.com/jbosstools/jbosstools-build-ci/commit/cab99f1346fff090d796b8df86ece1e8640dc511?w=1 (4.4.x branch)
https://github.com/jbosstools/jbosstools-build-ci/pull/138 (4.3.x branch)

Local tests indicate this works great - I added a *-debug* flag to make it easier to see why the script is returning "true" (SHAs differ) or "false" (SHAs are unchanged).

So I've added the new *-all* flag to the master job [2] config. Building...

[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-build-sites.aggregate.site_master/ >=11138

> create p2diff job to verify that nightly build is different from previous milestone
> -----------------------------------------------------------------------------------
>
>                 Key: JBIDE-16970
>                 URL: https://issues.jboss.org/browse/JBIDE-16970
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>    Affects Versions: 4.2.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.3.x
>
>
> After the discovery site build job is done, we should:
> * get a list of JIRAs for a given target fixversion, eg., 4.2.0.Beta1 or 8.0.0.Beta1 *job param* milestone = Beta1, Beta2, CR1, Final/GA (special case)
> * for respins, use *job param* label = "respin-a" or "respin-b" in jira query
> * filter query to only show the components and map those to actual project names - see https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTaskJIRAs.py#L83-L107 for mappings
> * install Eclipse from *job param* eclipseBundleVersion = luna.M6
> * install last milestone from *job param* oldURL = http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Beta1.core/
> * install Eclipse from *job param* eclipseBundleVersion = luna.M6 (in a different folder)
> * install new nightly from *job param* oldURL = http://download.jboss.org/jbosstools/updates/nightlycore/4.2.luna/
> * compare installed footprints - see https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/installAndDisplayCompositeSiteContent.sh
> * run p2diff on the two repos - see https://github.com/irbull/p2diff



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)