[
https://issues.jboss.org/browse/JBIDE-19598?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-19598:
-------------------------------
Description:
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...
was:
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 aggregate when
component has SCM changes.
This could be a replacement for the p2director job.
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
Fix For: 4.3.0.Beta1
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.11#6341)