ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #09055
Re: RTM silo management in CI Train
On Tue, Jul 15, 2014 at 8:20 PM, Kevin Gunn <kevin.gunn@xxxxxxxxxxxxx> wrote:
>
>
>
> On Tue, Jul 15, 2014 at 11:54 AM, Colin Watson <cjwatson@xxxxxxxxxx> wrote:
>>
>> For the plan to deliver the phone RTM from a derived "ubuntu-rtm"
>> distribution, we'll need to use a different set of silo PPAs, since PPAs
>> are attached to a particular distribution (which is clearer now that the
>> PPA URL format has been changed to include the distribution name).
>> Although there are a few remaining bits, Launchpad has mostly now been
>> extended to cope with non-Ubuntu PPAs, and it's time to think about how
>> we're going to handle this in CI Train.
>>
>> We probably just want to create another 20 silos for ubuntu-rtm once it
>> exists. The open questions are how to refer to them, and how to arrange
>> to land things in them. In the remainder of this mail I will refer to
>> PPAs consistently using their new ~OWNER/DISTRIBUTION/NAME scheme in an
>> attempt to minimise confusion.
>>
>> Note that Didier indicated in
>> https://lists.ubuntu.com/archives/ubuntu-release/2014-June/002898.html
>> that he thought the changes to cupstream2distro itself would be pretty
>> straightforward. I agree, for what it's worth.
>>
>> * Names? The current scheme is
>> ~ci-train-ppa-service/ubuntu/landing-{000..020}, with 000 being a
>> test silo. We could use
>> ~ci-train-ppa-service/ubuntu-rtm/landing-{021..040} to avoid having
>> to invent a new naming scheme. However, this is sort of non-obvious
>> to the uninitiated, it doesn't give us a nice space for a test silo,
>> and it cuts off further expansion of the ubuntu silos in case we need
>> that. Could we use
>> ~ci-train-ppa-service/ubuntu-rtm/landing-{000..020}? Launchpad will
>> permit this (PPAs are unique up to owner/distribution/name), so the
>> only question is whether this is clear enough.
>>
>> * How do we refer to these informally? Right now people say "silo 1"
>> etc. Perhaps "silo RTM-1"? I think it ought to be made clear when
>> you're landing something in the more tightly-controlled RTM archive.
>>
>
> somewhat dependent on the naming above, if you go with silos {000..020} on
> both ubuntu & ubuntu-rtm, you'll have to designate :)
> otherwise it'd be implied, if i'm in silo21 i'm rtm
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. I am in
favour of not using the numbers for stable vs. devel.
>
>>
>> * How will we handle this in the spreadsheet? My only thought so far
>> is that we should have a column for whether you're targeting RTM or
>> not. But I guess at the moment we have a destination series in the
>> "Assign to silo" menu entry, which is used for trusty builds - I
>> guess maybe that could be extended to include a distribution? Seems
>> a bit easy to make a mistake that way though.
>
>
> won't every project have an rtm branch (and a trunk) ? therefore, any MP
> targeting project-rtm would be for rtm ?...although, that might take some
> flexibility out of mixing rtm/ubuntu for debug/test purposes (non-landing
> silo builds).
I think all projects that have to diverge will have -rtm branch. All
projects that just land isolated fixes after we do the forking could
possible continue to deliver into trunk only and land in ubuntu-rtm
and ubuntu at the same time.
>
>>
>>
>> * 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.
>>
>> * Anything else?
>>
>> Thanks,
>>
>> --
>> Colin Watson [cjwatson@xxxxxxxxxx]
>>
>> --
>> Mailing list: https://launchpad.net/~ubuntu-phone
>> Post to : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>> More help : https://help.launchpad.net/ListHelp
>
>
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References