With the recent revamp of https://docs.centos.org, the rendering process was modified to use a single container, that is available publicly (https://quay.io/repository/centosci/mkdocs-centos) That means that all docs contributors can start using same container and so ensuring that it would be rendered the same way to real docs.centos.org vhost
As Docs SIG is still adding more features, we'd need (infra side) to help ensuring that needed features would automatically land in the built container.
I'd propose to : - have the Containerfile public so that people can open MR/PR against it - have quay.io built triggered (based on branch) automatically after a git merge - document container tag to use (and have latest pointing to the one we'd need to use)
latest
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: centos-build-pipeline, doc, feature-request, high-gain, medium-gain
Implement (so far) :
A commit (pushed or merged) at the gitlab side automatically triggers a rebuild and tags it with latest if coming from main branch, and staging tag if coming from staging branch
main
staging
We'll just test that it works fine and then adapt the ansible role to pull from new centos-infra org on quay.io and start tagging correct version to use
centos-infra
Role adapted and switched to new container pipeline
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.