Differences between revisions 5 and 6

Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 1. Please create a Pull Request at https://git.centos.org/centos/cbs-content-control .  1. Please create a Pull Request at https://git.centos.org/centos/cbs-content-control
Line 16: Line 16:
Example:

Steps to request space on the mirror network

  1. Please create a Pull Request at https://git.centos.org/centos/cbs-content-control

  2. You will need the following information:
    • SIG Name
    • CBS Release Tag(s) to combine into the final repo
    • Final directory location on mirror.centos.org
    • The expected format is the following :
          <tag>|<destination path>|<dir to run createrepo in>|<destination on mirror.centos.org>
          
  3. An exemple follows. You can check additional examples in the commits history.

cloud7-openstack-rocky-release/|7/cloud/x86_64/openstack-rocky/|7/cloud/x86_64/openstack-rocky/|7/cloud/x86_64/openstack-rocky/
cloud7-openstack-rocky-release/|7/cloud/ppc64le/openstack-rocky/|7/cloud/ppc64le/openstack-rocky/|7/cloud/ppc64le/openstack-rocky/ 

Worth noting that for CentOS 7, x86_64 will be pushed to mirror.centos.org/centos/$path while other arches like ppc64le/ppc64/aarch64 will be pushed to mirror.centos.org/altarch/$path. The $contentdir yum variable can be used in your .repo files to select the branch (centos or altarch).

Also worth noting that sign+push to mirror.centos.org happens only once a day, from Monday to Thursday, at 9AM UTC (altarch push being itself processed after that)

If you need help please open a bug on https://bugs.centos.org in the 'Community Build Service' component of the 'Buildsys' project.

SIGGuide/Content/Mirror (last edited 2019-10-04 06:58:31 by ThomasOulevey)