Common Build Infrastructure/Publishing/Helios
< Common Build Infrastructure | Publishing
Revision as of 04:09, 1 February 2010 by Nickboldt.gmail.com
To update your [.build file], simply set these properties in your promote.properties file. You must already have an existing file; these properties control updating your file and committing the changes to CVS, not [one from scratch].
# if set, update zip will be unpacked into destination dir and use synchMethod # above to add or replace contents targetUpdateDir=/home/data/httpd/download.eclipse.org/tools/ve/updates/1.5
# if set, this promote will publish this update site's information into a # .build file based on the template in the releng folder # you will still need to link to it from within the helios.build file, but # updates to this file can be done automatedly # for a remote file to be checked in via CVS, eg., for Helios @ Eclipse. Note # the use of colons (:). # or, can either point to relative-path file within your releng project for local testing #coordinatedReleaseBuildFile=vep15.build coordinatedReleaseBuildFile=:ext:email@example.com:/cvsroot/callisto:org.eclipse.helios.build/ve15.build
# if not set, targetUpdateURL will be calculated from targetUpdateDir, above # using this substitution: # /home/data/httpd/download.eclipse.org/* becomes # http://download.eclipse.org/* targetUpdateURL=http://download.eclipse.org/tools/ve/updates/1.5