canonical-ci-engineering team mailing list archive

[Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx>]

We have our team meeting tomorrow, and with it an opportunity to speak
to Didier about the architecture of the CI Train.

The deployment code lives in lp:ci-train. The business logic lives in
lp:cupstream2distro in the citrain/ directory.

You have admin access to https://ci-train.ubuntu.com. Note that this
is a production deployment. Do not change settings in it.

Finally, we also have the presentation Didier made on the Train to us
a while back:
https://www.youtube.com/watch?v=esRTXoIXa1w

It might also be worth looking back at lp:uci-engine to understand
things like whether multiuser support is as easy as removing some
failsafes in the lander.

By the end of the meeting tomorrow I want to know the list of tasks we
need to replace the Train with the Airline in the uce-0 milestone.
We'll assign out as many of these as we can on the same call.

So your questions for Didier should be those that wrap up your understanding.

We should also brainstorm on what will be better about the Airline
over the Train in this first deployment. Every time we have to migrate
UE over to a new system we should be providing them some value in
doing so. What manual process from the Train will the Airline replace
by the first release (June 2nd)?

For example:

10:58 AM <ev> didrocks: does the train do any kind of testing at all,
or is it just what's in `make check`? That is, this thing isn't
driving AP in any way or running dep-8 tests, right?
10:58 AM <didrocks> ev: no, it doesn't do any kind of integration, unfortunately

Thanks