[
https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-21145:
----------------------------------------
Thanks for clarifying that Pavol. So indeed, there is no need to trigger aggregation. So,
assuming we can rely on the check of JBIDE-19670 to decide whether to publish or not, I
believe we can simply get rid of the component-install job and have a scheduled build of
aggregator (that would publish only when now content is available).
Component-install job does not reliably install all JBT IUs and so
does not see changes between CI builds
---------------------------------------------------------------------------------------------------------
Key: JBIDE-21145
URL:
https://issues.jboss.org/browse/JBIDE-21145
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
Reporter: Pavol Srna
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
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-...
[1]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-...
[2]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site...
(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-site...
(latest build shows: "Nov 27, 2015 3:43 AM NOT PUBLISHED: UNCHANGED")
Please investigate.
Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)