Bug 496282 - Simplify "collect and process tests" logic to avoid "cron
job" on Releng HIPP 

- this is two stage fix. currently the file is taken as input for
collect.sh. this needs to change to accept command line arguments. Then
change the ep-collectResults job to call collect.sh directly. Instead of
having a file generated and running another cronjob.

This fixes the first part accepting the command line arguments. Once
this goes in I will make change to the ep-collectResults job.
This will get reduced to <path to collect.sh>/collect.sh $triggeringJob
$triggeringBuildNumber $buildId $eclipseStream $EBUILDER_HASH 

Change-Id: Ia59251dc1a86569111e316117304517feae97c80
Signed-off-by: Sravan Kumar Lakkimsetti <sravankumarl@in.ibm.com>
2 files changed
tree: 86897c919c74c6a5a3ee5da16094ebcc05ba4323
  1. .settings/
  2. eclipse-platform-parent/
  3. eclipse.platform.releng.prereqs.sdk/
  4. eclipse.platform.releng.tychoeclipsebuilder/
  5. production/
  6. scripts/
  7. .gitignore
  8. .gitmodules
  9. CONTRIBUTING
  10. pom.xml
  11. README.md
README.md

eclipse.platform.releng.aggregator

Aggregator repo for Eclipse SDK builds.

To run a complete build, on your local machine, run the commands from ./scripts/build.sh in this folder.

These commands requires the installation and setup of Java 1.8 or higher and Maven version 3.3.3 or higher Plus, other settings, alternatives, and other recommendations are made in the complete instructions on the Platform Build wiki. Note, it is highly recommended to use toolchains.xml and -Pbree-libs as decribed in Using BREE Libs. If you do use BREE Libs (with proper toolchains.xml file) you can use Java 1.7 to “run the build”.

Eclipse Platform Project committers should also read Automated Platform Builds.

Release Engineers should also be familiar with other documents on the Releng Wiki.

License

Eclipse Public License (EPL) v1.0