[
https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-21145:
---------------------------------------------
The proposal I went for was:
JBT aggregate build
p2 diff check comparing local JBT aggregate with last published JBT aggregate
local JBT aggregate p2 director install test
If there is no diff then the install test don't even need to run.
It still makes sense to have composite install tests running since not everyting is in
sync for aggregateand the composite - but
at least for the aggregate "chain of events" much less moving parts are needed
and you can skip the install tests in most cases.
Composite 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)