[jbosstools-issues] [JBoss JIRA] (JBIDE-18742) Only rely on rsync to publish new aggregate (remove other comparators)

Nick Boldt (JIRA) issues at jboss.org
Wed Feb 18 13:07:49 EST 2015


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

Nick Boldt commented on JBIDE-18742:
------------------------------------

This should be added to the new rsync.sh script (replaces publish.sh) [1] so that instead of an elaborate github check, we just check if the target has the same bits.

For non-aggregate publishes, we still need to do a github SHA check to determine if a fresh publish is needed. I can probably adapt something from my getProjectSHAs script [2] to achieve this.

[1] https://github.com/jbosstools/jbosstools-build-ci/pull/119
[2] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/getProjectSHAs.sh


> Only rely on rsync to publish new aggregate (remove other comparators)
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-18742
>                 URL: https://issues.jboss.org/browse/JBIDE-18742
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>            Reporter: Mickael Istria
>            Assignee: Nick Boldt
>             Fix For: 4.3.0.Alpha2
>
>
> 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.11#6341)


More information about the jbosstools-issues mailing list