D

debci

continuous integration system for Debian

Project ID: 18235
  • Antonio Terceiro's avatar
    lxc/create-testbed: avoid cleaning up valid containers · 2bee4565
    Antonio Terceiro authored
    Sometimes, the creation of a new testbed fails for various reasons (some
    essential package) breaks debootstrap, or something fails to download.
    Those failures are already handled by autopkgtest-build-lxc: the old
    container is only replaced by the new one in case of success.  In that
    case, it's OK for debci to just keep using the older container since it
    will be upgraded before running any tests anyway.
    
    The only case where we indeed want to remove containers is when the
    customizations needed by debci are not successfully applied.
    2bee4565
Name
Last commit
Last update
backends Loading commit data...
bin Loading commit data...
chroots Loading commit data...
config Loading commit data...
data Loading commit data...
debian Loading commit data...
docs Loading commit data...
etc/schroot/debci Loading commit data...
lib Loading commit data...
log Loading commit data...
public Loading commit data...
spec Loading commit data...
test Loading commit data...
tools Loading commit data...
.ackrc Loading commit data...
.ctags Loading commit data...
.gitignore Loading commit data...
.gitlab-ci.yml Loading commit data...
COPYING Loading commit data...
Makefile Loading commit data...
Procfile Loading commit data...
README.md Loading commit data...
TODO.otl Loading commit data...
Vagrantfile Loading commit data...
config.ru Loading commit data...
links Loading commit data...