test installation of .deb's #593

New Issue

zooko · 2009-01-23T23:45:06Z

zooko commented

2009-01-23 23:45:06 +00:00

Have a buildbot step asserting that dpkg -i allmydata-tahoe-$VERSION.deb works.

This was originally mentioned in #434 (automate testing of installation).

Have a buildbot step asserting that `dpkg -i allmydata-tahoe-$VERSION.deb` works. This was originally mentioned in #434 (automate testing of installation).

zooko added the

labels 2009-01-23 23:45:06 +00:00

zooko added this to the undecided milestone 2009-01-23 23:45:06 +00:00

warner commented

2009-01-26 23:14:35 +00:00

As discussed on IRC the other week, this could use the 'debootstrap' and 'schroot' tools. The idea would be to have a chroot environment for the test, and not touch the buildslave's host OS at all. The first buildstep should be to checkout the tahoe source and build a .deb . The second step should be to create a new chroot environment (from the same distribution as the host, say, a "gutsy" chroot environment), with some basic level of functionality, using packages that are cached on the host so it won't require a huge download each time. This chroot should have an /etc/apt/sources.list that points at the allmydata.org APT repository. The third step should be to copy the .deb into the chroot and do some sort of 'apt-get install allmydata-tahoe', using it, such that any dependencies are pulled from the .org repo. The fourth step should be to run 'trial allmydata' inside the chroot and make sure it succeeds. The fifth step should be to run 'tahoe --version' inside the chroot.

This ought to validate:

the .deb is installable
the .deb's dependencies are available on allmydata.org
the /usr/bin/tahoe that gets installed is runnable
all dependencies are useable/importable/compatible

From the description of the 'schroot' package, it looks like it might contain sudo-style tools to allow non-root users to create and manipulate chroot environments. The 'debootstrap' package contains tools to create debian installations inside a chroot.

As discussed on IRC the other week, this could use the 'debootstrap' and 'schroot' tools. The idea would be to have a chroot environment for the test, and not touch the buildslave's host OS at all. The first buildstep should be to checkout the tahoe source and build a .deb . The second step should be to create a new chroot environment (from the same distribution as the host, say, a "gutsy" chroot environment), with some basic level of functionality, using packages that are cached on the host so it won't require a huge download each time. This chroot should have an /etc/apt/sources.list that points at the allmydata.org APT repository. The third step should be to copy the .deb into the chroot and do some sort of 'apt-get install allmydata-tahoe', using it, such that any dependencies are pulled from the .org repo. The fourth step should be to run 'trial allmydata' inside the chroot and make sure it succeeds. The fifth step should be to run 'tahoe --version' inside the chroot. This ought to validate: * the .deb is installable * the .deb's dependencies are available on allmydata.org * the /usr/bin/tahoe that gets installed is runnable * all dependencies are useable/importable/compatible From the description of the 'schroot' package, it looks like it might contain sudo-style tools to allow non-root users to create and manipulate chroot environments. The 'debootstrap' package contains tools to create debian installations inside a chroot.

warner commented

2009-03-12 20:59:28 +00:00

this has been merged into #630.

warner added the

duplicate

label 2009-03-12 20:59:28 +00:00

warner closed this issue

2009-03-12 20:59:28 +00:00

Sign in to join this conversation.