3890
Comment: remove stuff which is already in trunk/TODO
|
3891
|
Deletions are marked like this. | Additions are marked like this. |
Line 52: | Line 52: |
* 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 |
* todo * codebase related: http://svn.debian.org/viewsvn/piuparts/trunk/TODO * piuparts.debian.org related: http://svn.debian.org/viewsvn/piuparts/piatti/README.txt |
Contents
General info
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.
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 results are available at http://piuparts.debian.org
Machine info
piuparts.cs.helsinki.fi aka piatti.debian.org
hosted at Department of Computer Science, University of Helsinki
donated by HP
- dual AMD Opteron(tm) Processor 275, 2.2 Ghz
- 8GB RAM
- 300 GB physical volume for data
How piuparts is setup on piatti
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: svn.debian.org/piuparts
mailing list: piuparts-devel@l.a.d.o
commit diff list: piuparts-commits@l.a.d.o
- todo
codebase related: http://svn.debian.org/viewsvn/piuparts/trunk/TODO
piuparts.debian.org related: 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.)