veyepar: ci/autopkgtest BoF

Author(s):	Antonio Terceiro
Location	Bo
Date	aug Sun 06	Days Raw Files
Start	12:00	First Raw Start	error-in-template
Duration	00:45:00	Offset	None
End	12:45	Last Raw End
Chapters
Total cuts_time	None min.

https://debconf17.debconf.org/talks/35/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf ciautopkgtest_BoF.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

The idea for this session it to get together and as discuss all things autopkgtest/Debian CI and any related aspects. If you have ideas on how to test your package but don't know exactly how to wire things up for running with autopkgtest, want to share your joy and/or your frustration with the tools or with the environments, or have tips or questions on writing autopkgtest tests, this is for you.

autopkgtest runs tests on binary packages. The tests are run on the package as installed on a testbed system (which may be found via a virtualisation or containment system). The tests are expected to be supplied in the corresponding Debian source package. See adt-run(1) and /usr/share/doc/autopkgtest. Depending on which virtualization server you want to use, you need to install additional packages (schroot, lxc, lxd, or qemu-system)

Debian CI (ci.debian.net) runs autopkgtest against the entire Debian archive, Adding autopkgtest tests to your package will automatically make those tests run on Debian CI as soon as the package hits the archive.

Comment:

production notes