We have a need to be able to generate embargoed content for SIGs. As an example, Xen publishes embargoed content where we need to apply patches, build an SRPM and then binary RPMs.
We can not do this in an open build system as the content must be embargoed until after the release date.
What I think we need is password protected input and builds in the CBS and password protected repos for the resultant RPMs. We could then control access to those specific locations via login.
Does the current version of koji support that?
If not, we could create an embargoed build area(s) in the current CentOS build system, where the output of the build system is not transferred to buildlogs.centos.org .. but I would also need to point to the proper repos in the CBS as well.
Who, besides the Xen rpms in the virt SIG might need this embargoed build capability?
Thanks, Johnny Hughes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Aug 27 14:33, Johnny Hughes wrote:
We have a need to be able to generate embargoed content for SIGs. As an example, Xen publishes embargoed content where we need to apply patches, build an SRPM and then binary RPMs.
We can not do this in an open build system as the content must be embargoed until after the release date.
What I think we need is password protected input and builds in the CBS and password protected repos for the resultant RPMs. We could then control access to those specific locations via login.
Does the current version of koji support that?
Koji doesn't support "hiding" builds, so we can probably do what you suggested below. (I believe embargo builds were kicked around as a feature in the Koji v2 discussion)
If not, we could create an embargoed build area(s) in the current CentOS build system, where the output of the build system is not transferred to buildlogs.centos.org .. but I would also need to point to the proper repos in the CBS as well.
Who, besides the Xen rpms in the virt SIG might need this embargoed build capability?
Thanks, Johnny Hughes
- --Brian
hi,
On 27/08/15 20:33, Johnny Hughes wrote:
We have a need to be able to generate embargoed content for SIGs. As an example, Xen publishes embargoed content where we need to apply patches, build an SRPM and then binary RPMs.
We can not do this in an open build system as the content must be embargoed until after the release date.
What I think we need is password protected input and builds in the CBS and password protected repos for the resultant RPMs. We could then control access to those specific locations via login.
Does the current version of koji support that?
If not, we could create an embargoed build area(s) in the current CentOS build system, where the output of the build system is not transferred to buildlogs.centos.org .. but I would also need to point to the proper repos in the CBS as well.
Who, besides the Xen rpms in the virt SIG might need this embargoed build capability?
when i asked you to come up with this plan, the intention was that we need to offer this to every SIG and every component within the SIG. We need to also be able to run this sort of a service for content we host in CentOS Extras.
so the process we come up with needs to apply across the board, and we need to document it well.
-
Brian Stinson -
Johnny Hughes -
Karanbir Singh