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

Nick Boldt (JIRA) issues at jboss.org
Fri Dec 18 10:20:00 EST 2015


     [ https://issues.jboss.org/browse/JBIDE-16970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt closed JBIDE-16970.
------------------------------
    Fix Version/s: 4.3.1.Beta1
                   4.4.0.Alpha1
                       (was: 4.3.x)
       Resolution: Done


Appears to be working and too onerous for QE to verify (requires reading lots of build logs and comparing the output to github to check for changes), so closing. 

I won't add p2diff to the component site builds because by definition those IUs are different for every build (new timestamp, new BUILD_NUMBER). Sure, we could filter all that out and just check for 3rd party IU changes (eg., angular and tern in the JST builds) but that would ALSO be caught by the SHA check, so the extra level achieves nothing.

> create mechanism 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.1.Beta1, 4.4.0.Alpha1
>
>
> 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)


More information about the jbosstools-issues mailing list