|
Size: 4672
Comment: thank HP too :)
|
Size: 1895
Comment: CategoryPackaging
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| [[TableOfContents(2)]] | #language en |
| Line 3: | Line 3: |
| = general info = 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! ... = machine info = * hosted at [http://cs.helsinki.fi/index.en.html Department of Computer Science, University of Helsinki] * donated by [http://hp.com/go/debian/ HP] * dual AMD Opteron(tm) Processor 275, 2.2 Ghz * 4GB RAM * 465 GB physical volume for data * 50 GB for /home for piatti * 90 GB for mirror * 10 GB for xenu1 (testdomain) * 4 GB and 128 MB swap for test.my.piuparts (testdomain2 :) * X GB piuparts slave * Y GB developer test environtments * wishlist: 30-50 GB for svn-buildstat * 2 IPs = 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 == * install xen-shell & tools * put all scripts and configs into svn * set up xenu domains with fai * use the same documentation for fai as for debian-community * IMO every member of the piuparts alioth group should have the right to commit configuration for the XENU domains (no extra repo/access control) * only a few people can commit that config to a machine (sudoers) * root access for XENU domains for DDs and non-DDs (like goneri if needed, or other qa members), via debian ud-ldap (for DDs) or local accounts (for non-DDs) * discuss this with DSA * XENU domain for svn-buildstat (min 30gb hd space) * mirror proposed updates and security updates too * run two piuparts slaves to make use of the two cpus * 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: |
=== What is piuparts? === |
| Line 89: | Line 6: |
| %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: https://piuparts.debian.org |
| Line 109: | Line 19: |
| = documentation = | === piuparts.debian.org === |
| Line 111: | Line 21: |
| split this wiki page into subpages, so that the piuparts documentation can be mainained in the wiki, by exporting as docbook. | piuparts is being run constantly on all suites of the main Debian archive, the results are made public on [[https://piuparts.debian.org|piuparts.debian.org]]. The [[piuparts/piuparts.debian.org|piuparts.debian.org setup]] is documented and maintained in GIT, plus there is also an [[piuparts/FAQ|FAQ]] available. |
| Line 113: | Line 24: |
| suggested structure: | === Documentation === |
| Line 115: | Line 26: |
| * /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 |
piuparts itself has a [[https://piuparts.debian.org/doc/README.html|README]] and a [[http://piuparts.debian.org/doc/piuparts.1.html|manpage]] - read those before reading the [[piuparts/HowTos]]. === Contributing === If you are interested in contributing, that's great! Here's a list to hopefully get you started: * join [[piuparts/Development|development]] efforts. Every little pull request helps. Check the BTS for plenty of wishlist bugs to tackle. * [[https://piuparts.debian.org/bug_howto.html|file bugs]] based on piuparts.d.o runs! * improve the documentation, both these wiki pages and what's in GIT has been growing over the years and it's showing. ---- ## This page is referenced from http://piuparts.debian.org CategoryPermalink CategoryPackaging |
What is 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: https://piuparts.debian.org
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. The piuparts.debian.org setup is documented and maintained in GIT, plus there is also an FAQ available.
Documentation
piuparts itself has a README and a manpage - read those before reading the piuparts/HowTos.
Contributing
If you are interested in contributing, that's great! Here's a list to hopefully get you started:
join development efforts. Every little pull request helps. Check the BTS for plenty of wishlist bugs to tackle.
file bugs based on piuparts.d.o runs!
- improve the documentation, both these wiki pages and what's in GIT has been growing over the years and it's showing.