-
Bug
-
Resolution: Done
-
Blocker
-
4.3.1.Beta1, 4.4.0.Alpha1
-
None
We have often seen old artifacts on nightly sites (mars and neon too).
It seems that the composite-install job [0], [1] is not reliable. So, the downstream JBT aggregate builds [2], [3] are not triggered automatically to pick up all new changes in the upstream JBT component site builds.
[0] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_master/lastBuild/console
[1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_4.3.mars/lastBuild/console
[2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/ (latest build shows: "Nov 27, 2015 6:15 AM NOT PUBLISHED: UNCHANGED")
[3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_4.3.mars/ (latest build shows: "Nov 27, 2015 3:43 AM NOT PUBLISHED: UNCHANGED")
Please investigate.
Thanks!
- is related to
-
JBIDE-21215 IUs missing from snapshot update site while site is being published / outdated metadata needs to be refreshed within Eclipse
- Closed
- relates to
-
JBIDE-21169 Add openshift.cdk feature into JBT Core update site
- Closed
-
JBIDE-16970 create mechanism to verify that nightly build is different from previous milestone
- Closed