Currently koji doesn't have any read access controls, or at least not any related to builds. Most folks would probably either use a private koji, or just run mock against koji's yum repos. Are we really only talking about a scratch build type scenario, or do folks want a real build that is hidden? Difference being that in the former case, you'd end up running a non-scratch rebuild after the embargo lifts, while in the latter you'd flip a switch and have the build appear. The latter case is much harder (and also begs for embargo lockdown in source control), but neither is trivial to implement. On Thu, Sep 25, 2014 at 12:25 PM, Karanbir Singh <mail-lists at karan.org> wrote: > hi guys, > > we need a way to build embargo'd content like reimzul's priv-build, that > does not make stuff public till a specific date ( the actual push to > public can be manual ); > > how would we achieve this on cbs ? I guess the git stuff is easier since > it can just be a scratch build from srpm and people need not push the > git content back to git.centos.org till embargo expiry. > > - KB > > -- > Karanbir Singh > +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh > GnuPG Key : http://www.karan.org/publickey.asc > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > http://lists.centos.org/mailman/listinfo/centos-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20140925/b6d10ee5/attachment-0008.html>