[
https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-21145.
------------------------------
Resolution: Done
TL;DR:
Max agrees the composite should continue to run, and has no comments about changing the
frequency of the aggregate build's github check for changes or its simple scheduled
builds.
Denis agrees p2diff can be used where we don't have .qualifiers that change for each
build (ie., for component builds)
Since I've added p2diff checks to the JBT & JBDS aggregate builds I believe can
therefore be closed.
If you feel I've missed something, please open a new JIRA to capture that missing
requirement.
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.4.0.Alpha1
Attachments: jbide21145-conflict-between-tp-and-central.png
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)