]
Nick Boldt commented on JBIDE-16970:
------------------------------------
Above change applied in
AFTER build 11317. Will need to let this grind for a few iterations to see if it works as
expected.
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/createTaskJ...
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.Bet...
* 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/instal...
* run p2diff on the two repos - see
https://github.com/irbull/p2diff