[jbosstools-issues] [JBoss JIRA] (JBIDE-16614) skipRevisionCheckWhenPublishing is misleading in aggregators

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-16614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978680#comment-12978680 ] 

Nick Boldt commented on JBIDE-16614:
------------------------------------

jbosstools-build-sites.aggregate.site_master checks github for changes every 8 hrs. Admittedly, it finds such changes rarely. However, it is also triggered by https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_master/ which checks the composite site every 3 hours. 

If the contents of the composite have changed, because an upstream project has published new content, then it will trigger all the downstream aggregates, setting skipRevisionCheckWhenPublishing=true. Each of those downstream jobs will in turn ALSO  set skipRevisionCheckWhenPublishing=true so the whole stack is then rebuilt - all the aggregates, the installer, and the install-test jobs too. Then the discovery build fires, and the install grinder fires after that.

As long as the upstream components successfully build & publish, then the composite will be updated and every 3 hours you'll have a new JBT and JBDS build. Isn't that good enough?

> skipRevisionCheckWhenPublishing is misleading in aggregators
> ------------------------------------------------------------
>
>                 Key: JBIDE-16614
>                 URL: https://issues.jboss.org/browse/JBIDE-16614
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>    Affects Versions: 4.2.0.Alpha2
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>             Fix For: 4.2.0.Beta1
>
>
> As the *aggregate* and devstudio-product_* are only run for good reasons (change in a component, or change in aggregation repository - category.xml and other, there is no reason why using the skipRevisionCheckWhenPublishing, which is furthermore a bit error prone and misleading (some manual builds are ignored whereas there has been changes).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)