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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-16614:
----------------------------------------

What happens when there is no Git change and skipRevisionWhenPublishing is set to true? I would expect the job to publish anyway because most builds are a cascade of an upstream change.
I would be pretty happy with a "skipPublishingWhenOutputIsSimilar", but the skipRevisionWhenPublishing flag is not relevant since source change in aggregator represent a very minimal part of our builds. That's why I'm suggesting to remove this flag and publish independently of revision on the aggregator Git repository.

> 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)