Only official builders should be able to start an official build job

[Paul Sokolovsky]

We require a user to be a member of "official builders" group to be able to create/edit "official" job. However, anyone can still start such job. This may be not desirable, for example for release builds, which once done, released and announced, should stay without any changes.

One obvious way for this is to require "official builders" membership for starting an official build.

[Alexander Sack (asac)]

so currently we have three types of builds split up in two categories:

 1. official tip/continuous
 2. official release
 3. user builds

not sure if we should start differentiate ACLs and retention of 1. and 2. by introducing another

I would think for 1. we want >30 days no matter how many builds; for 2. we want never delete and for 3. something reasonably short (like one week or at least 7 builds)

[Alexander Sack (asac)]

"by introducing another ..." build type/UI tab etc.

[Paul Sokolovsky (pfalcon)]

Yes, build retention is related, but different matter in context of this bug - do we want to limit who can start official builds or no? I guess looking forward, like adding support for community builds, etc. this makes sense.

[Zach Pfeffer (pfefferz)]

I think this bug takes the discussion in the wrong direction - though I'm glad you filed it Paul. With CI we'll have official builds coming out everyday/hour etc. We should just be able to just mark one of the many builds that completes as "official" and have the build system automatically retain it - the build system could automatically save the pinned manifest on the release branch and kick off the release build from it. We could then gate the people who could save builds.

[Paul Sokolovsky (pfalcon)]

On Wed, 10 Aug 2011 22:33:56 -0000
Zach Pfeffer <email address hidden> wrote:

> I think this bug takes the discussion in the wrong direction - though
> I'm glad you filed it Paul. With CI we'll have official builds coming
> out everyday/hour etc. We should just be able to just mark one of the
> many builds that completes as "official" and have the build system
> automatically retain it - the build system could automatically save
> the pinned manifest on the release branch and kick off the release
> build from it. We could then gate the people who could save builds.

This bug is about build system as it is now, not about
CI-yet-to-be-done.

--
Best Regards,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

[Paul Sokolovsky (pfalcon)]

Retention settings improvements submitted as #832000 .

[Paul Sokolovsky (pfalcon)]

Seems this caught not interest, closing.