[jbosstools-issues] [JBoss JIRA] (JBIDE-16970) create mechanism 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=13136351#comment-13136351 ] 

Nick Boldt commented on JBIDE-16970:
------------------------------------

Please elaborate on your cryptic phrase "actual updates". I am led to believe that if the sources in the git repo changes, and the bits are rebuilt, they'll be new, different, upversioned, etc., thus making any source change an "actual update."

Is there something else you think a p2 diff will capture that a souce diff won't? Some new third party bits sucked into the build will likely ALSO cause a source change (a new version of some runtime needed to build forge or openshift or hibernate, for example). Some new URL for a new version of angular or tern will also be reflected in the root pom of those projects (jst, javaee, etc.).

So... can you demonstrate how to make an "actual update" in the composite or aggregate site that is not the result of an upstream SOURCE change?

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