-
Enhancement
-
Resolution: Done
-
Major
-
4.2.0.Beta1
-
None
-
Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015
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
- is related to
-
JBIDE-16957 no difference between beta1 and beta1a updatesites
- Closed
-
JBIDE-21145 Composite install job does not reliably install all JBT IUs and so does not see changes between CI builds
- Closed
-
JBIDE-16614 skipRevisionCheckWhenPublishing is misleading in aggregators
- Closed
-
JBIDE-18742 Only rely on rsync to publish new aggregate (remove other comparators and checks)
- Closed
- relates to
-
JBIDE-19072 Improve plugin version auditing & how we build
- Closed
-
JBDS-3208 reorg/refactor directories for consistency across JBT/JBDS
- Closed
-
JBIDE-20177 migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo
- Closed