Diff for "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

-  ⇤ ← Revision 16 as of 2007-11-29 18:15:21 → 
  Size: 2243
  Editor: LarsWirzenius
  Comment:
+   ← Revision 90 as of 2014-05-20 11:13:23 → ⇥
  Size: 2766
  Editor: HolgerLevsen
  Comment: move to piuparts/Development
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-= general info =
+#language en
 Line 3:
-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 :)
+<<TableOfContents(2)>>
 Line 5:
-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 =

 * alioth project
 * http://wiki.debian.org/SummerOfCode2007/PiupartsImprovements

= random todo-stuff =

 * split /fails/ into more directories
 * <liw> (at some point) you may want to run as piupartsm the bin/mirror-debian script
 * look at the irssi_away script to see how to monitor screen sessions, to notify when piuparts is hanging
 * backup /etc (and?)
 * also use the machine to run vlosuts 

= 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:
+= Overview about piuparts =
-Line 46:
+Line 8:
-%s = source package name
%v = source package version
%p = piuparts version
+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
}}}
-Line 50:
+Line 21:
-/source/%s -> index page
/source/%s/status -> status from last run
/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
+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 56:
+Line 23:
-/binary-i386/%s/%v
/binary-.../%s/%v
/status/%s
    -> "OK"
    -> "FAIL"
+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 62:
+Line 25:
-/%s -> /source/%s
}}}
+= Advanced usage tips for piuparts =
 * This obviously implies you are familar with the manpage, README_1st and README_server :-D
 * [[piuparts/UseCases]]

= Ressources about piuparts.debian.org & distributed testing =

 * 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]]

----
## This page is referenced from http://piuparts.debian.org
CategoryPermalink