Mercurial > treepkg
view demopublishpackages.cfg @ 557:9824e409388b
Refactor git branching
If a checkout is already available and the branch is changed in
the config git command would always fail because it doesn't know
the branch to track. Therefore always check if the branch is
locally available and if not checkout the remote branch
author | Bjoern Ricks <bricks@intevation.de> |
---|---|
date | Fri, 02 Sep 2011 08:45:28 +0000 |
parents | 25ef11a79d7f |
children |
line wrap: on
line source
# Demo configuration file for publishpackages.py. The default config # file used by publishpackages.py is publishpackages.cfg, so to use this # file as the basis for your configuration, copy or rename this file and # adapt it to your needs. [publishpackages] # Distribution (e.g. etch, lenny, ...) and section (e.g. experimental, # unstable, ...) for which to publish the packages distribution: lenny section: experimental # Number of newest successfully built revisions to publish for each # track. Ignored when publishpackages is called with an explicit # revision. num_newest: 3 # Username and host on which the treepackager runs. publishpackages.py # has to be able to connect to that host as the builduser via ssh # without knowning the password. This is best achieved with the # ssh-agent. build_user: builder build_host: localhost # the program to run on build_host to list the filenames of the packages # in question. Currently publishpackages.py assumes that the default # configuration for that program works. build_listpackages: ~/treepkg/bin/listpackages.py # Username and host on which to publish the packages. # publishpackages.py uses ssh to execute commands on the publish_host to # create directories and rsync to copy the files from the local cache to # the publish_host. If publish_host is empty, the publishpackages.py # assumes that no ssh or other remote login is needed to access the # publish host with the right permissions. publish_user: builder publish_host: localhost # the directory on the publish_host where the apt directories reside. publish_dir: /home/ftp/apt/dists/ # If true publishpackages.py will remove the packages in publish_dir # that were not put there by the current run. Setting it to True is # probably only useful when using publishpackages.py to automatically # publish the newest built packages using a cron-job, for instance. publish_remove_old_packages: False # Command to run after the packages have been copied to the publish # host. This command is run on the host running publishpackages.py. after_upload_hook: ssh %(publish_user)s@%(publish_host)s /home/ftp/apt/update # local cache directory. publishpackages.py may delete it and its # contents, so if you intend to run publishpackages.py on the same # system for several remote instances of treepkg, make sure the # directory name is unique enough, to avoid one publishpackages instance # removing the files of another. # # The value is passed through the python functions os.expanduser and # os.expandvars, so references to home directories of the form ~ or # ~user at the beginning of the value and environment variable # references of the form $VAR or ${VAR} are expanded. cachedir: /tmp/${LOGNAME}/treepkg-package-cache/%(build_host)s cachedb: /tmp/${LOGNAME}/treepkg-package-cache/%(build_host)s-cache.db