[
https://issues.jboss.org/browse/JBIDE-18742?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-18742:
------------------------------------
Please note that the above code fails if there's no pre-existing update site in
http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/
Needs a better bootstrap check -- eg., if site can't be hit with wget (returns 404)
then set publish=true and skip trying to p2diff.
Also needs to be rolled out to the rest of the 4.3.mars and master jobs.
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
Fix For: 4.3.0.Alpha1
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)