ubuntu-phone team mailing list archive

[Didier Roche <didrocks@xxxxxxxxxx>]

Hey,

I couldn't discuss that in today's session of the landing process, so 
I'm using that opportunity to announce some visible CI Train changes 
based on lander's feedback:

* Automatic tracking of landing progress of your components
-> once you published your components, you have to wait it to be in the 
release pocket to merge and clean. Previously, the status was only known 
when you click on merge and clean (to know where your components were, 
in NEW, -proposed, lost... :p).
Now, the status field of the spreadsheet is automatically updated and so 
you know if your component is stucked anywhere in the publication 
process (like in -proposed) after an unusual amount of time and work on 
that, or if you can just run "merge and clean".

* Ability to reconfigure yourself your silos if you don't add new components
-> Adding commits just need a rebuild. However, if you add/drop MPs, you 
had to ask for a "silo reconfiguration" from the landing team.
This is going to be available to the lander now. If you just add/remove 
MPS and don't add new components that were not part of the initial set 
(as we still need to keep ordering and avoid conflicts), you will be 
able, on the silo tab, to just click "reconfigure" and paste there the 
MPs list as well as source packages list. The landing team will be there 
to help you for your first reconfiguration ;)

* Special "overriding component lock" case for justified landings.
-> For very very identified and special case (like Qt 5.2 landing), the 
locks that you have on your trunks can take ages. Especially, when you 
just have a rebuild on the other side. So the possibility to override 
the lock by the landing team in those special situations + redoing the 
rebuild on the other side will be given to you.
Just be aware that it means that some building and testing work will 
then be invalidated (the first who lands win) and rebuilding/reconciling 
and testing will need to be redone. It's just an override, no the main 
use case!

When can we have that you will ask?
Well... it's already in and in production, so as of today :)
Enjoy!

Cheers,
Didier

PS: as a bonus, you will probably have noticed that there is a new 
header in the CI Train spreadsheet[1] showing which last promoted is, 
what the last built image, DEFCON levels as discussed in the session + 
some general information about the image and landing states.

[1] 
https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFlCc1VzeVZzWmdBZS11WERjdVc3dmc&usp=drive_web#gid=0