Re: Moving daily builds out of main debian-cloud-images project
On 9/1/19 12:40 PM, Bastian Blank wrote:
> Hi folks
>
> As mentioned during the last meeting, I would like to move the daily
> builds out of the main debian-cloud-images project. The new project
> reponsible for them would exist in a different group, so we don't longer
> need to guard access to the main cloud-team group that strict.
>
> Disadvantages of this move:
> - Visibility of daily builds is reduced as they are in a new group.
> - Code and config updates for now need explicit changes in the -daily
> (and the same in the already existing -release) repo to become active.
>
> Advantages:
> - Access credentials for vendor and Debian infrastructure only exist in
> the new group, so accidently leaking them is way harder.
> - All jobs in this new group will run on Debian infrastructure.
> - We gain the possibility to actually test upload procedures, which may
> need access to credentials.
>
> Any objections?
>
> Regards,
> Bastian
Hi,
If I understand well, you're moving ahead with having all done by the
Salsa CI. That's really not what I envisioned. I though we'd be moving
to build things on Casulana, at the same time as the ISO images.
The Salsa CI usually runs on Google cloud. We of course have less trust
in that, than a Debian machine. It's also very slow, and not in sync
with the Debian release process, which would make a lot more sense
compared to the current daily build.
As a cloud user, I very much prefer to have images when needed, compared
to a daily build for which I'm not sure I need an update. I'd see moving
to that, instead of the perfect process Steve has implemented, as a
regression.
Your thoughts?
Cheers,
Thomas Goirand (zigo)
Reply to: