[jbosstools-issues] [JBoss JIRA] (JBIDE-18662) use getProjectSHAs.sh to control when to run aggregate builds, instead of doing composite site installs
Mickael Istria (JIRA)
issues at jboss.org
Wed Nov 19 06:18:39 EST 2014
[ https://issues.jboss.org/browse/JBIDE-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mickael Istria closed JBIDE-18662.
----------------------------------
Fix Version/s: (was: 4.2.1.Final)
Resolution: Duplicate Issue
> use getProjectSHAs.sh to control when to run aggregate builds, instead of doing composite site installs
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18662
> URL: https://issues.jboss.org/browse/JBIDE-18662
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.CR2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Alpha1
>
>
> Nick said:
> >> How else would you determine if/when the aggregates should be built?
> >> Using a variation on getProjectSHAs.sh script and diffing the last run
> >> w/ the current run? Or something else?
> And Mickael replied:
> > It could be built as often as the composite-install job runs because it
> > takes more or less the same time, and even if one builds aggregator for
> > nothing, it won't change the aggregate repository output (only the
> > content.jar and artifact.jar would be updated to a newer timestamp).
> > So since it's totally possible directly aggregate whenever something
> > changes for the same price, it seems more straightforward to do it
> > instead of introducing an intermediary control job, which can have bugs.
> Then Nick said:
> Yeah, I still like the fact that the composite install job performs an install test... but maybe it can be downstream of the TP change and NOT upstream of the aggregate builds?
> I could look at creating a more "diffable digest" as output of getProjectSHAs.sh and have that run in Jenkins as the gatekeeper (or keymaster?) for when to run aggregates.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
More information about the jbosstools-issues
mailing list