-
Enhancement
-
Resolution: Won't Do
-
Major
-
None
-
None
-
Sprint #2 April 2015
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
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
Another benefit is that it allows us to get rid of the composite (1 less couple of files to maintain)
- is related to
-
JBIDE-18662 use getProjectSHAs.sh to control when to run aggregate builds, instead of doing composite site installs
-
- Closed
-
-
-
- Closed
-
- relates to
-
JBIDE-19072 Improve plugin version auditing & how we build
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
