As you're all aware now, CentOS CI infra landscape will be different in the next weeks/months.
One of the biggest change will be the introduction of Duffy v3 as replacement for the Duffy API and while there will be compatibility layer (allowing you to use your existing "cico" workflow), the goal is that each tenant will move to the new api, which itself then requires either: - you abusing directly the api endpoint (https://duffy.ci.centos.org/docs) - use the new duffy client (pip3.8 install --user duffy[client] with a config file
We'd like to offer the duffy client natively in our cico-workspace pod/container that is automatically deployed for your jenkins jobs on openshift cluster.
But if we trigger it, it will also come with something additional : the current centos Stream8 based container is using ansible 2.9.x, which is now deprecated, and kicking a container rebuild would automatically install ansible-core 2.12.x (present in el8 natively now)
As you're aware, ansible-core doesn't have all the modules that you probably need to use for your workflow, so instead of install the meta-pkg ansible (which then install almost everything) you can come (reply to this thread) with a list of collections that you'd like to see in the base container (the less we have to pull, the better, to keep the container image as light as possible), we'd then add these to the container image.
Thanks for your collaboration,
On 21/06/2022 16:23, Fabian Arrotin wrote:
As you're all aware now, CentOS CI infra landscape will be different in the next weeks/months.
One of the biggest change will be the introduction of Duffy v3 as replacement for the Duffy API and while there will be compatibility layer (allowing you to use your existing "cico" workflow), the goal is that each tenant will move to the new api, which itself then requires either:
- you abusing directly the api endpoint (https://duffy.ci.centos.org/docs)
- use the new duffy client (pip3.8 install --user duffy[client] with a
config file
We'd like to offer the duffy client natively in our cico-workspace pod/container that is automatically deployed for your jenkins jobs on openshift cluster.
But if we trigger it, it will also come with something additional : the current centos Stream8 based container is using ansible 2.9.x, which is now deprecated, and kicking a container rebuild would automatically install ansible-core 2.12.x (present in el8 natively now)
As you're aware, ansible-core doesn't have all the modules that you probably need to use for your workflow, so instead of install the meta-pkg ansible (which then install almost everything) you can come (reply to this thread) with a list of collections that you'd like to see in the base container (the less we have to pull, the better, to keep the container image as light as possible), we'd then add these to the container image.
Thanks for your collaboration,
No feedback received (yet) so I guess we'll start with just ansible-core and *no* collection
-
Fabian Arrotin