General info

Description: .deb package installation, upgrading, and removal testing tool

piuparts is being run constantly on piuparts.debian.org - that URL links to more general information about piuparts too.

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

• code analysis and more on ohloh

How piuparts is setup on piuparts.debian.org

Running piuparts is the boring, automated part and is supervised by Luk and Holger, who can su into the piupartss (slave) user. piuparts-slave 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.

Twice a day, at 6 and 18 UTC, piuparts-reports 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

Machine info

• piuparts.cs.helsinki.fi aka piatti.debian.org aka piuparts.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

Howto setup a piuparts test-instance for development

*to be written*

Piuparts and PTS integration suggestion

this specification has been implemented but a simpler one. This notes are kept here for reference and shall be deleted soon.

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

/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
    %s fuzzy $URLto_stats_page ([http://piuparts.debian.org/squeeze/state-waiting-for-dependency-to-be-tested.html example page])

And really unknown, ie not listed in that file.


The earlier idea of having the piuparts version included there has been overthrown: on new tests, the successful test shall be reseted. The version is in the log anyway :)

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.)

CategoryPermalink