Setup: You need to file a bug report at https://bugs.centos.org/ against Project: Buildsys and Component: Community buildservice to include the cbs.centos.org TAG you want to promote along with the destination url you want the content to show up at. As an example look at : https://bugs.centos.org/view.php?id=10213#c25473
Submit the data in this format:
<tag>|<destination path>|<dir to run createrepo in>|<destination on buildlogs> Example: sclo7-rh-nodejs4-rh-testing/|7/sclo/x86_64/rh/rh-nodejs4/|7/sclo/x86_64/rh/|7/sclo/x86_64/rh/ sclo7-rh-mongodb32-rh-testing/|7/sclo/x86_64/rh/rh-mongodb32/|7/sclo/x86_64/rh/|7/sclo/x86_64/rh/ sclo7-rh-mongodb30upg-rh-testing/|7/sclo/x86_64/rh/rh-mongodb30upg/|7/sclo/x86_64/rh/|7/sclo/x86_64/rh/ sclo7-rh-python35-rh-testing/|7/sclo/x86_64/rh/rh-python35/|7/sclo/x86_64/rh/|7/sclo/x86_64/rh/ sclo7-rh-ruby23-rh-testing/|7/sclo/x86_64/rh/rh-ruby23/|7/sclo/x86_64/rh/|7/sclo/x86_64/rh/ sclo7-rh-ror42-rh-testing/|7/sclo/x86_64/rh/rh-ror42/|7/sclo/x86_64/rh/|7/sclo/x86_64/rh/
- Once setup, the CBS tag will be checked every 2 hours for new content, and when available, will be pushed to buildlogs.centos.org to the destination repository setup. This requires no manual intervention, beyond you tagging the right rpms to the -testing repositories.
Note the CentOS admins require at least one build to be tagged into -testing in order to fully configure buildlogs.centos.org, because the internal "sync" script does not publish empty repositories for sanity+safety reasons. If your -testing tag does not contain any builds, please tag at least one build into -testing before opening the buildlogs.centos.org configuration ticket.
Note that this configuration is completely independent of the mirror.centos.org configuration. This particular configuration tells the buildlogs.centos.org server to host content tagged as "-testing". You must request a second mapping configuration for mirror.centos.org for the content you tag as "-release".