comparison demopublishpackages.cfg @ 256:8052aabada8b

Make publishpackages.py work for automated regular publishing of the newest built packages. This requires changes in the configuration file as well, so demopublishpackages.cfg is updated too.
author Bernhard Herzog <bh@intevation.de>
date Thu, 16 Apr 2009 09:32:35 +0000
parents 70735b398bb0
children 0542181b8452
comparison
equal deleted inserted replaced
255:70735b398bb0 256:8052aabada8b
6 [publishpackages] 6 [publishpackages]
7 # Distribution (e.g. etch, lenny, ...) and section (e.g. experimental, 7 # Distribution (e.g. etch, lenny, ...) and section (e.g. experimental,
8 # unstable, ...) for which to publish the packages 8 # unstable, ...) for which to publish the packages
9 distribution: lenny 9 distribution: lenny
10 section: experimental 10 section: experimental
11
12 # Number of newest successfully builts revisions to publish for each
13 # track. Ignored when publishpackages is called with an explicit
14 # revision.
15 num_newest: 3
11 16
12 # Username and host on which the treepackager runs. publishpackages.py 17 # Username and host on which the treepackager runs. publishpackages.py
13 # has to be able to connect to that host as the builduser via ssh 18 # has to be able to connect to that host as the builduser via ssh
14 # without knowning the password. This is best achieved with the 19 # without knowning the password. This is best achieved with the
15 # ssh-agent. 20 # ssh-agent.
21 # configuration for that program works. 26 # configuration for that program works.
22 build_listpackages: ~/treepkg/bin/listpackages.py 27 build_listpackages: ~/treepkg/bin/listpackages.py
23 28
24 # Username and host on which to publish the packages. 29 # Username and host on which to publish the packages.
25 # publishpackages.py uses ssh to execute commands on the publish_host to 30 # publishpackages.py uses ssh to execute commands on the publish_host to
26 # create directories and scp to copy the files from the local cache to 31 # create directories and rsync to copy the files from the local cache to
27 # the publish_host. 32 # the publish_host. If publish_host is empty, the publishpackages.py
33 # assumes that no ssh or other remote login is needed to access the
34 # publish host with the right permissions.
28 publish_user: builder 35 publish_user: builder
29 publish_host: localhost 36 publish_host: localhost
30 37
31 # the directory on the publish_host where the apt directories reside. 38 # the directory on the publish_host where the apt directories reside.
32 publish_dir: /home/ftp/apt/dists/ 39 publish_dir: /home/ftp/apt/dists/
33 40
34 # Command to execute on the build host to update the apt archive 41 # If true publishpackages.py will remove the packages in publish_dir
35 publish_apt_archive_update: /home/ftp/apt/update 42 # that were not put there by the current run. Setting it to True is
43 # probably only useful when using publishpackages.py to automatically
44 # publish the newest built packages using a cron-job, for instance.
45 publish_remove_old_packages: False
46
47 # Command to run after the packages have been copied to the publish
48 # host. This command is run on the host running publishpackages.py.
49 after_upload_hook: ssh %(publish_user)s@%(publish_host)s /home/ftp/apt/update
36 50
37 # local cache directory. publishpackages.py may delete it and its 51 # local cache directory. publishpackages.py may delete it and its
38 # contents, so if you intend to run publishpackages.py on the same 52 # contents, so if you intend to run publishpackages.py on the same
39 # system for several remote instances of treepkg, make sure the 53 # system for several remote instances of treepkg, make sure the
40 # directory name is unique enough, to avoid one publishpackages instance 54 # directory name is unique enough, to avoid one publishpackages instance
This site is hosted by Intevation GmbH (Datenschutzerklärung und Impressum | Privacy Policy and Imprint)