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 65 as of 2009-09-03 05:19:33 → 
  Size: 4365
  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 5:
-= General info =
+= Overview about piuparts =
 Line 8:
-Description: .deb package installation, upgrading, and removal testing tool
+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 11:
+Line 21:
-piuparts is being run constantly on [[http://piuparts.debian.org|piuparts.debian.org]] - that URL links to more general information about piuparts too.
+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 13:
+Line 23:
-A [[http://wiki.debian.org/piuparts/FAQ|FAQ]] is also available.
+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 15:
+Line 25:
-= Developing piuparts =
+= Advanced usage tips for piuparts =
 * This obviously implies you are familar with the manpage, README_1st and README_server :-D
 * [[piuparts/UseCases]]
-Line 17:
+Line 29:
- * 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]]
 * 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]]
 * [[http://www.ohloh.net/p/9038|code analysis]] and more on ohloh
+= Ressources about piuparts.debian.org & distributed testing =
-Line 27:
+Line 31:
-= Developing piuparts, the rewrite of version 2 =

 * stalled
 * planning stage
 * in bzr: bzr get http://code.liw.fi/piuparts2/bzr/trunk/ (may move to bzr.debian.org later)
 * will take at least a year until piuparts1 becomes obsolete

== From the BoF at Debconf9 ==

 * new output format: http://lists.debian.org/debian-devel/2009/07/msg00662.html
 * piuparts should not fail just because dependencies fail

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

Once a day at midnight 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 [[http://db.debian.org/machines.cgi?host=piatti|piatti.debian.org]] aka piuparts.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

= 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.)
+ * 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]]