|
Size: 3566
Comment:
|
Size: 2766
Comment: move to piuparts/Development
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| [[TableOfContents(2)]] | #language en |
| Line 3: | Line 3: |
| = general info = | <<TableOfContents(2)>> |
| Line 5: | Line 5: |
| piuparts runs on piuparts.cs.helsinki.fi aka piatti.debian.org and just like lintian and linda should be run on every developer machine before uploading :) piuparts logs (currently outdated) are available at [http://piatti.debian.org http://piatti.debian.org] #debian-qa is the irc-channel to coordinate work on irc, piuparts-devel is the project name on alioth. = how to run piuparts on piatti = the piuparts stuff is partly in the piupartsm account (master end, including debmirroring), and partly in the piuartss account (the slave, which actually runs piuparts) run piuparts-slave.py as piupartss and watch it run via screen. the slave starts the master when it needs it, you don't need to start it manually also read http://liw.iki.fi/liw/debian/piuparts-logfile-processing-howto If you want to help, please don't bother liw, h01ger has access too and you should bother him. ... to be continued! ... = troubleshouting/maintainance = Sometimes the chroot tarballs in /home/piupartss/ need to be removed, currently there are sid.tar.gz and sarge.tar.gz see /etc/piuparts/piuparts-slave.conf = developing piuparts = * alioth project * http://wiki.debian.org/SummerOfCode2007/PiupartsImprovements = todo = == machine related == * rm /home and mv to lvm * recreate mirror * install xen-shell & tools * put all scripts and configs into svn * mirror proposed updates and security updates too * finish aide configuration - http://wiki.debian.org/Teams/DSA/MachineSetup (but: <buxy> h01ger: AFAIK, aide is not consistently used (and is known to break on merkel currently), so you can probably skip that part for now) * drop Joey a note so that all users are replicated via ldap * backup /etc and /org via http://wiki.debian.org/Teams/DSA/DaBackup * also use the machine to run svnbuildstat.debian.net * also use the machine to run vlosuts done: * apt-get install debian.org aide nagios-nrpe-server lvm2 * apt-get install -t etch-backports xen-shell xen-tools == codebase related == * split /fails/ into more directories * <liw> (at some point) you may want to run the bin/mirror-debian script as user piupartsm * look at the irssi_away script to see how to monitor screen sessions, to notify when piuparts is hanging = piuparts and pts integration suggestion = In order for the PTS to be able to display piuparts testing status for a package, and link to its log file, Piuparts could generate a set of static files that will be visible via http: |
= Overview about piuparts = |
| Line 67: | Line 8: |
| %s = source package name %v = source package version %p = piuparts version /source/%s -> index page /source/%s/%v -> a particular log /source/%s/latest -> log for latest version /source/%s/piuparts-%p/%v -> a particular log from a version of piuparts similar for /binary-$ARCH/ /%s -> /source/%s For PTS integration: one file with results for all source packages: /results-per-source.txt %s pass $MATCHINGLOG %s fail $MATCHINGLOG |
Description: .deb package installation, upgrading, and removal testing tool piuparts tests that .deb packages (as used by Debian) handle installation, upgrading, and removal correctly. It does this by creating a minimal Debian installation in a chroot, and installing, upgrading, and removing packages in that environment, and comparing the state of the directory tree before and after. piuparts reports any files that have been added, removed, or modified during this process. . piuparts is meant as a quality assurance tool for people who create .deb packages to test them before they upload them to the Debian package archive. Homepage: http://piuparts.debian.org |
| Line 87: | Line 21: |
| = documentation = | piuparts is being run constantly on all suites of the main Debian archive, the results are made public on [[http://piuparts.debian.org|piuparts.debian.org]]. |
| Line 89: | Line 23: |
| split this wiki page into subpages, so that the piuparts documentation can be mainained in the wiki, by exporting as docbook. | piuparts itself has a [[http://piuparts.debian.org/doc/README_1st.html|README_1st]] and a [[http://piuparts.debian.org/doc/piuparts.1.html|manpage]], for the piuparts.debian.org setup there is also an [[http://wiki.debian.org/piuparts/FAQ|FAQ]] available. |
| Line 91: | Line 25: |
| suggested structure: | = Advanced usage tips for piuparts = * This obviously implies you are familar with the manpage, README_1st and README_server :-D * [[piuparts/UseCases]] |
| Line 93: | Line 29: |
| * /piuparts - index page, just a table of contents * /piuparts/about - what is piuparts * /piuparts/devel - information how to participate in piuparts development * /piuparts/doc/software - piuparts documentation * /piuparts/doc/piatti - documenation about piuparts.cs.helsinki.fi * /piuparts/todo - todo list |
= Ressources about piuparts.debian.org & distributed testing = * piuparts.d.o reports list: [[http://lists.alioth.debian.org/mailman/listinfo/piuparts-reports|piuparts-reports@l.a.d.o]] * [[http://piuparts.debian.org/doc/README_server.html|README_server]] * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=blob;f=README_pejacevic.txt;hb=HEAD|README_pejecevic.txt]] - information how the setup has been made together with [[Teams/DSA|DSA]]. * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=blob;f=instances/piuparts.conf.pejacevic|instances/piuparts.conf.pejacevic]] is installed as /etc/piuparts/piuparts.conf on both the host acting as master as well as the slave. * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=blob;f=conf/distros.conf|conf/distros.conf]] is installed as /etc/piuparts/distros.conf (also on all hosts). * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=tree;f=custom-scripts|custom-scripts]] are installed into /etc/piuparts/scripts (also on all hosts). * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=blob;f=instances/piuparts.conf.anbe|instances/piuparts.conf.anbe]] * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=blob;f=instances/piuparts.conf.goldwasser|instances/piuparts.conf.goldwasser]] ---- ## This page is referenced from http://piuparts.debian.org CategoryPermalink |
Contents
Overview about piuparts
Description: .deb package installation, upgrading, and removal testing tool piuparts tests that .deb packages (as used by Debian) handle installation, upgrading, and removal correctly. It does this by creating a minimal Debian installation in a chroot, and installing, upgrading, and removing packages in that environment, and comparing the state of the directory tree before and after. piuparts reports any files that have been added, removed, or modified during this process. . piuparts is meant as a quality assurance tool for people who create .deb packages to test them before they upload them to the Debian package archive. Homepage: http://piuparts.debian.org
piuparts is being run constantly on all suites of the main Debian archive, the results are made public on piuparts.debian.org.
piuparts itself has a README_1st and a manpage, for the piuparts.debian.org setup there is also an FAQ available.
Advanced usage tips for piuparts
- This obviously implies you are familar with the manpage, README_1st and README_server :-D
Ressources about piuparts.debian.org & distributed testing
piuparts.d.o reports list: piuparts-reports@l.a.d.o
README_pejecevic.txt - information how the setup has been made together with DSA.
instances/piuparts.conf.pejacevic is installed as /etc/piuparts/piuparts.conf on both the host acting as master as well as the slave.
conf/distros.conf is installed as /etc/piuparts/distros.conf (also on all hosts).
custom-scripts are installed into /etc/piuparts/scripts (also on all hosts).