Differences between revisions 17 and 18
Revision 17 as of 2007-11-29 19:02:14
Size: 2299
Comment:
Revision 18 as of 2007-11-30 15:25:09
Size: 2566
Editor: HolgerLevsen
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[TableOfContents(2)]]
Line 32: Line 34:
= random todo-stuff = = todo =

== machine related ==

 * rm /home and mv to lvm
 * recreate mirror
 * install xen-shell & tools
 * put all scripts and configs into svn
 * set up ud-ldap
 * backup /etc (and?)
 * also use the machine to run svnbuildstat.debian.net
 * also use the machine to run vlosuts

== codebase related ==
Line 35: Line 50:
 * <liw> (at some point) you may want to run as piupartsm the bin/mirror-debian script  * <liw> (at some point) you may want to run the bin/mirror-debian script as user piupartsm
Line 37: Line 52:
 * backup /etc (and?)
 * also use the machine to run vlosuts

?TableOfContents(2)

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

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

todo

  • rm /home and mv to lvm
  • recreate mirror
  • install xen-shell & tools

  • put all scripts and configs into svn
  • set up ud-ldap
  • backup /etc (and?)
  • also use the machine to run svnbuildstat.debian.net
  • also use the machine to run vlosuts

  • 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:

%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