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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-16970:
---------------------------------------------

Another downside of relying on buildinfo.json to do these checks is that they rely on stuff only availble on jenkins or specific download.jboss.org servers (i.e. something have had to publish the .json file)

p2diff just needs the previous and newly built site, nothing else. Can even run 100% locally.

Also, if something went wrong in publish so the buildinfo.json is updated but the site failed to update - buildinfo.json would say stuff changed, but actually hadn't.

I'm not saying which is best - just saying relying on buildinfo.json is not the most obvious choice and could introduce even more coupling to specific systems making it harder to have our buildsetup be movable/scalable.

Thus just something to be aware and conscious about.

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