canonical-ci-engineering team mailing list archive

[Chris Lee <chris.lee@xxxxxxxxxxxxx>]

Hi All,

We (the Tools and Trust team, CC'd in this email) have a request for a
special Jenkins job that will assist in making Autopilot releases as
painless and speedy as possible.

Currently for a release of Autopilot to happen there is a lot of
manual testing done which takes a long time (a day or so) for someone
to do.

This testing is effectively a collection of the automated test jobs
that are already exist.

Our idea is to create one massive Jenkins job that contains all (or a
subset?) of the existing automated acceptance tests across the board
(including Click, Touch, Desktop etc.) that can be used to green-light
an Autopilot release.

This job won't be run very often (only when we intend to release) so
it shouldn't tie up resources and doesn't matter if it takes hours to
complete.

Autopilot touches so many different test suites, environments and form
factors (desktop and device) and we need to be confident that a
release won't break the build. It is getting harder and taking longer
to manually run the tests and can also be a moving target (a contrived
example; the CI test runner script using an app-armor command that the
manual tester isn't aware of, causing the tester grief)

We're hoping to be able to harness the existing infrastructure and
test suites to make this whole process a lot easier.

So the questions are: Can we have this please? and what are the steps
needed to make it happen?

TnT guys, am I missing any details or important points?


Regards,
Chris