The Debian continuous integration (debci) is an automated system that coordinates the execution of automated tests against packages in the Debian system. debci will continuously run autopkgtest test suites from source packages in the Debian archive.

The {file:docs/MAINTAINERS.md FAQ for package maintainers} contains useful information on how to declare the test suite, how the test is executed, how to reproduce the test runs locally, etc.

Additionally, we have these extra tutorial-style documentation:

• {file:docs/TUTORIAL.md Functional testing of Debian packages}, a tutorial transcribed from a DebConf15 talk on autopkgtest and debci is available that covers declaring test suites, issues to consider, and tips and tricks. ∙ [https://deb.li/pattestdeb](Patterns for Writing As-Installed Tests for Debian Packages) is a paper describing patterns (as in "design patterns") for writing tests for Debian packages.

See the {file:docs/INSTALL.md installation guide} for instructions on how to deploy debci to your own infrastructure.

Please report bugs against the debci package in the Debian BTS.

• Get source: git clone https://alioth.debian.org/anonscm/git/collab-maint/debci.git
• Browse source
• {file:docs/HACKING.md How to setup a development environment}
• {file:docs/RUBYAPI.md The Ruby API to the debci data store}

For maintainer queries and general discussion:

• mailing list: [email protected]
• IRC: #debian-qa on OFTC. Feel free to highlight terceiro

For the development of debci itself

• mailing list: autopkgtest-devel
• IRC: #debci on OFTC

Copyright © the debci development team.

debci is free software licensed under the GNU General Public License version 3 or later.