[jbosstools-issues] [JBoss JIRA] (JBIDE-18742) Use p2diff to determine whether to publish new aggregate

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-18742:
----------------------------------------

I'm currently making experiment with job jbosstools-build-sites.aggregate.coretests-site_master
I can easily detect whether there are some changes to publish, however, the publish.sh script decides to look at SCM changes (there are none) and does't publish the new contents... I'll to set the skipRevisionCheckBlah flag to true by default, but I believe the condition should check if SCM or p2diff has changes.

> Use p2diff to determine whether to publish new aggregate
> --------------------------------------------------------
>
>                 Key: JBIDE-18742
>                 URL: https://issues.jboss.org/browse/JBIDE-18742
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>            Reporter: Mickael Istria
>
> Instead of the composite-install test to decide whether we aggregate or not, it would be simpler to build aggregation in any case and then use p2diff (or other smart mechanism) to decide whether we want to publish the new composite or not.
> It's more or less just a matter of scripting
> {code:none}
> p2diff file:${WORKSPACE}/results/${JOB_NAME}/all/repo/ http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/ | grep -e ^\< -e ^\> > p2diff_snapshot
> if [[ -s p2diff_snapshot ]]; then
>    ./publish.sh
> fi
> {code}
> Another benefit is that it allows us to get rid of the composite (1 less couple of files to maintain)



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)