[
https://issues.jboss.org/browse/JBIDE-19598?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-19598:
---------------------------------------------
downstream-ext-plugin was already in use when I did buildchow so it was added a while
back:
https://review.openstack.org/#/c/158117/
and now I grok it - got mislead by the "composite-install *test* jobs" and
thought it was install tests, not tests if publish was needed.
But how do we avoid the downstream ext plugin to trigger if SCM has changed, but the build
content has not ?
without check we are back to aggregation happen way too often are we not ?
Use "Build other project (extended)" to cascade
aggregation
-----------------------------------------------------------
Key: JBIDE-19598
URL:
https://issues.jboss.org/browse/JBIDE-19598
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Affects Versions: 4.3.0.Alpha2
Reporter: Mickael Istria
Assignee: Mickael Istria
Priority: Minor
Fix For: 4.3.0.Beta2
In order to decide whether to cascade aggregation when components are build, we could use
the "Build other project (extended)" plugin in order to trigger 2 aggregate jobs
(site, coretests-site) when component has SCM changes.
This would require changing all 17 component jobs (per stream = 34 jobs), but would
eliminate the need for the composite-install test jobs [1].
[1]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)