[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=13142119#comment-13142119 ] 

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

Found a way to enable p2diff, but not with the Nexus zip as it needs an extra step and the snapshot in Nexus could disappear unexpectedly (as it did for me).

So, using the static snapshot build in /home/hudson/static_build_env/jbds/p2diff/ is better. Also tried to enable this as a maven build plugin step but this turned out to be way simpler, even when dealing with matrix jobs and their ridiculoously long paths (including invalid chars like "!" in p2 URL paths):

{code}
p2diff=/home/hudson/static_build_env/jbds/p2diff/x86$(if [[ $(uname -a | grep x86_64) ]]; then echo _64; fi)/p2diff
# work around invalid chars in a matrix job's workspace path using symlink magic
tmpdir=$(mktemp -d); pushd $tmpdir >/dev/null; ln -s ${WORKSPACE} ws; popd >/dev/null

if [[ ${skipRevisionCheckWhenPublishing} == "true" ]] || [[ $([[ -x $p2diff ]] && ${p2diff} file://${tmpdir}/ws/sources/aggregate/${projectName}-site/target/fullSite/all/repo/ http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-build-sites.aggregate.${projectName}-site_${jbosstools_site_stream}/latest/all/repo/ -vmargs -Dosgi.locking=none | egrep "<|>") ]] || [[ $(. ${WORKSPACE}/sources/util/checkLatestPublishedSHA.sh -s ${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo -t http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-build-sites.aggregate.${projectName}-site_${jbosstools_site_stream}/latest/all/repo/ -all) == "true" ]]; then
# deploy here
fi
rm -fr $tmpdir
{code}


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