Thursday, 2 April 2015

ATTENTION! CI Train spreadsheet broken, workaround migration to a new one!

Attention CI Train landers!

Even though Robert is actively working on the spreadsheet replacement to
(hopefully) get us rid of all the various Google Spreadsheet incidents
in the CI Train, currently this is still something that requires time to
finalize. As you all know the spreadsheet once again went into a broken
state yesterday which caused a lot of grief for all its users and

After wasting some time trying to get it back into a working state, I
have decided that it makes no sense to continue trying to revive it or
waiting for Google problems resolving itself. I think that every time
before, whenever we thought some change fixed the spreadsheet, it was
actually unrelated and the back-end simply stabilized by itself (or got
fixed by Google). It all seems random.

Taking all that into account we decided to migrate to a new spreadsheet.
We already did that in the past and it's probably time to do it once
again. You can find the new link in the standard redirect:

The title of the spreadsheet should be:
"CI Train (new spreadsheet)"

Be sure to fetch the new spreadsheet key and use that instead of the old
one in any scripts you are using. We are aware that this is not the
solution to the problem at all, but this was the fastest thing we could
do to resume everyone's normal workflow. The proper solution is being
worked on as we speak.

Let's hope this will last until we have a replacement in place.

Please remember that since the spreadsheet was reverting itself multiple
times during the few days, some landings might be missing and require
re-adding. Same for silos that have been reconfigured. We will try,
using CI Train backups, getting as many missing ones back but it would
be best if every team could double-check their landings.

We apologize for all the inconveniences.

Thank you.

Best regards,

Ɓukasz 'sil2100' Zemczak
Foundations Team

ubuntu-devel mailing list
Modify settings or unsubscribe at: