|
Size: 4412
Comment: update to current reality
|
Size: 2766
Comment: move to piuparts/Development
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| = General info = | = Overview about piuparts = |
| Line 8: | Line 8: |
| Description: .deb package installation, upgrading, and removal testing tool | Description: .deb package installation, upgrading, and removal testing tool |
| Line 15: | Line 15: |
| . | . |
| Line 18: | Line 18: |
| Homepage: http://piuparts.debian.org | |
| Line 20: | Line 21: |
| piuparts is being run constantly on piuparts.cs.helsinki.fi aka piatti.debian.org - and/but just like lintian it also should be run on every developer machine before uploading :) | 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 22: | Line 23: |
| piuparts results are available at [[http://piuparts.debian.org|http://piuparts.debian.org]] | 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 24: | Line 25: |
| == Machine info == | = Advanced usage tips for piuparts = * This obviously implies you are familar with the manpage, README_1st and README_server :-D * [[piuparts/UseCases]] |
| Line 26: | Line 29: |
| * piuparts.cs.helsinki.fi aka [[http://db.debian.org/machines.cgi?host=piatti|piatti.debian.org]] * 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 * 8GB RAM * 300 GB physical volume for data |
= Ressources about piuparts.debian.org & distributed testing = |
| Line 33: | Line 31: |
| == How piuparts is setup on piatti == | * 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]] |
| Line 35: | Line 40: |
| Running piuparts is the easy, automated part and is supervised by Luk and Holger, who can su into the piupartss (slave) user. piuparts-slave.py is run in a shared screen session and seldom needs interaction. The piupartss user needs to be able to run piuparts and thus can use sudo without restrictions. The slave automatically starts the master, to reserve packages to process and to pass logfiles to the master. Ideally all members of the Debian-QA group can su to the piupartsm user and process the logfiles - currently it's again only Luk and Holger. piupartsm has no special privileges. If you want to help, please join #debian-qa and say so there. Every hour piuparts-reports.py is run as piupartsm by cron to generate the html output of the logs. For more information see http://svn.debian.org/viewsvn/piuparts/piatti/README.txt = Developing piuparts = * alioth project * source code: [[http://svn.debian.org/viewsvn/piuparts/|svn.debian.org/piuparts]] * mailing list: [[http://lists.alioth.debian.org/mailman/listinfo/piuparts-devel|piuparts-devel@l.a.d.o]] * commit diff list: [[http://lists.alioth.debian.org/mailman/listinfo/piuparts-commits|piuparts-commits@l.a.d.o]] * codebase related todo: http://svn.debian.org/viewsvn/piuparts/trunk/TODO * piuparts.debian.org related todo: http://svn.debian.org/viewsvn/piuparts/piatti/README.txt * there was a [[SummerOfCode2007/PiupartsImprovements]] == 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: {{{ %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 }}} /!\ Problem: PTS is source package centered, piuparts binary package. {{{ For Ubuntu development weather report (similar to PTS): a file with the following: Pass: %d Fail: %d }}} (See https://blueprints.launchpad.net/ubuntu/+spec/developer-weather-report for the Ubuntu developer weather report.) == Documentation == split this wiki page into subpages, so that the piuparts documentation can be mainained in the wiki, by exporting as docbook. update: use asciidoc suggested structure: * /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 |
---- ## 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).