This repo contains the configuration of the Ansible Content CI https://ansible.softwarefactory-project.io/zuul/status.
This directory contains the list of projects that are enabled. Edit these files to add, remove or rename a project in Zuul.
To add new repos into Zuul, it's a two step process:
First, you MUST enable the softwarefactory-project-zuul https://github.com/apps/softwarefactory-project-zuul/ application in your Github project. If the project is in the ansible-collections/ https://github.com/ansible-collections namespace, you don't have to do anything.
- Add to resources/ansible.yaml
note: Follow up to the merge of the PR, Zuul will refresh its configuration. The job is called update-config. For various reason, the update may fail, you can take a look at the previous runs here: https://ansible.softwarefactory-project.io/zuul/builds?job_name=config-update&project=ansible/zuul-config
- Add to zuul.d/projects.yaml
note: You don't need to do it if the project satisfies the rules specified in the file. For example, rule 1 and rule 2 say that if a collection's repository name starts with ansible-collections/community* or sap-linux/community* and the repository has the main branch as default, the repository will be included in the project and published by Zuul on Galaxy automatically when a git tag is created in the collection's repo. In this case, only PR1 above is required.
note: In case you have a community.* collection in the github.com/ansible-collections/ organization, you need to add your collection to the explicit regular expression that enables the publish-to-galaxy-3pci template if you do not have an equivalent of the Galaxy importer test running in GHA.
If you want to let Zuul merge the new PRs you need to add a label called mergeit to your project. The branch also need to be protected, like this example:
Matrix Chat Room https://matrix.to/#/#zuul:ansible.com