Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

DSDP/MTJ/Releng/Scripts

< DSDP‎ | MTJ‎ | Releng
Revision as of 10:36, 29 December 2008 by Wds057.motorola.com (Talk | contribs)

Scripts

There are six scripts available in the scripts folder of the org.eclipse.mtj.releng plug-in.

All these scrips use the bootstrap build.sh available in the org.eclipse.mtj.releng plug-in root.


build.sh

Usage :

setup.sh [-buildId name] [-metadata] [-revision tag] [-publish [-outputDirectory directory]] [-updateSite [-updateSiteDirectory directory]] [-notify] [-sign] [-runTests] M|N|I|S|R"

Arguments :

buildId : The name to be used in the build.

metadata : Generates P2 metadata.

revision : Reflects the svn version tag of the code to be used in the build.

publish : Indicates if the mtj packages will be copied to the download server.

outputDirectory : The directory in which mtj packages will be placed after the build process if the -publish argument is set. By default, the /home/data/httpd/download.eclipse.org/dsdp/mtj/downloads/drops/ directory is assumed.

updateSite : Indicate if an update site should be generated.

updateSiteDirectory : The directory in which mtj will post the update site files if the -updateSite argument is set. By default, the /home/data/httpd/download.eclipse.org/dsdp/mtj/updates/ directory is assumed.

notify : Indicate if the notification email must be sent after the build process. [Not Implemented]

sign : Indicate if the packages must be signed.

runTests : Indicate if the automatic test must be run. [Not Implemented]


Nightly scrips

Used to generate an official build and publish it in the download server under /home/data/httpd/download.eclipse.org/dsdp/mtj/downloads/drops/ and create an update site at /home/data/httpd/download.eclipse.org/dsdp/mtj/updates/0.9/NightlyBuilds/


Developer scrips

Used to run the same process of an official build, but, instead of publish it in the download server, it copy the resulting drop to /opt/public/dsdp/mtj/test/drops/ and create an update site at /opt/public/dsdp/mtj/test/drops/update/

Back to the top