Those get triggered whenever the package in question, or any of its dependencies, get updated in proposed (ubuntu proposed, not devel-proposed image).
AFAIK the long-term plan is to transition all non-make-check (e.g. autopilot, qml UI tests) to autopkgtests, meaning there's a standard way to execute them (DEP-8) locally or remotely.
The first thing that should happen, IMO, is they should be run in -ci jobs for packages that ship them, hence the ubuntu-ci-services-itself task.
FWIW it is being run in proposed already:
http:// d-jenkins. ubuntu- ci:8080/ view/Utopic/ view/AutoPkgTes t/job/utopic- adt-unity- scopes- api/
Those get triggered whenever the package in question, or any of its dependencies, get updated in proposed (ubuntu proposed, not devel-proposed image).
AFAIK the long-term plan is to transition all non-make-check (e.g. autopilot, qml UI tests) to autopkgtests, meaning there's a standard way to execute them (DEP-8) locally or remotely.
The first thing that should happen, IMO, is they should be run in -ci jobs for packages that ship them, hence the ubuntu- ci-services- itself task.