← Back to team overview

ubuntu-phone team mailing list archive

Re: RTM silo management in CI Train

 

On Tue, Jul 15, 2014 at 11:24 AM, Alexander Sack <asac@xxxxxxxxxxxxx> wrote:
> if we use the numbers to infer if its stable vs. devel, please make a
> big buffer (e.g. make all stable silos start with 5XX) so we can grow
> silos without having to make the scheme more complicated.

Yeah, I was going to say, why not 1XX or something, 5XX would also be
good. Then we don't paint ourselves in the corner with the numbering.



On Tue, Jul 15, 2014 at 11:19 AM, Alexander Sack <asac@xxxxxxxxxxxxx> wrote:
> I anticipated the least work on infrastructure side would be do
> duplicate the spreadsheet and point that as the ubuntu-rtm target. Not
> perfect, but as its not really a long lasting thing we are inventing
> here

Oh please, no. Then when we find a bug in the code, we have to fix it
in two places. And claiming it will be short-lived doesn't make it ok,
because these things always stick around longer than you anticipate.

I don't expect it to be especially difficult to have a new column with
some data validation so that the cells only accept either 'ubuntu' or
'ubuntu-rtm' and then you can pick them like a drop-down, and then
that can be trivially referenced when assigning. There's no need to
duplicate the entire spreadsheet for this.



>>  * Presumably the backend and the dashboard would both need to be
>>    extended.  I'm not familiar with the details here and would welcome
>>    commentary from those who are.
>
> Easiest might be to also duplicate the backend jenkins. It's already
> charged afaik, so duplicating that for ubuntu-rtm might be easy.

I'm not sure what charged means in the context of jenkins, but it
shouldn't be hard to just change the few places where we hard-code
'ubuntu' into a variable that can either be 'ubuntu' or 'ubuntu-rtm'
and reference that from the spreadsheet data.


Follow ups

References