Hi all CI infra tenants/users,
As a follow-up wrt previous mail about cico-workspace container update (see https://lists.centos.org/pipermail/ci-users/2021-October/002184.html) we had a look at what was needed to rebase the cico-workspace container to CentOS 8-stream.
We've built a container that you can start using with the following specs: - based on centos 8-stream - so having python3 (instead of python2), important for your jobs - still providing python-cicoclient (python3 version) - ansible 2.9.27 - git
This container is actually available as staging tag, so it's not *yet* the one that is automatically pulled through your jenkins as "cloud/container" node to run your jobs.
We'd like you to start testing your jobs against that updated cico-workspace, at your earliest convenience, so that you have a chance to eventually adapt your jobs, or ask us to add/change something in that container.
See the next items
# How to test ? The current DeploymentConfig used in openshift will provide jenkins, itself configure to pull cico-workspace from quay.io (quay.io/centosci/cico-workspace:latest) But you can also , as you have full admin rights in your own jenkins namespace, temporary switch to :staging tag.
To proceed, just log into your own jenkins apps on openshift/ocp.ci and follow the next steps:
Manage Jenkins Manage Nodes and Clouds (under System Configuration) Configure Clouds (on the left menu) Expand Kubernetes and under Pod template you'll see "cico-workspace" "Pod Template details" Containers Just swap quay.io/centosci/cico-workspace:latest => quay.io/centosci/cico-workspace:staging Apply/Save
You can now test your job (test job) and see if that still works or if you need to adapt something
# How to revert ? Assuming that you want to revert to :latest test (still c7 based), just proceed as above and swap back to quay.io/centosci/cico-workspace:latest
#When will you enforce the change ?
We have no fixed date in mind but we'd like to enforce this early december, which would give you enough time to fix your jobs (if there is a need to). We can also provide an alternative through a different tag like :c7 while we'd have c8s for :latest and you'd then be also able to modify your jobs to just continue to use older c7 container (not adviced though, but we'll continue to rebuild the container for security updates automatically)
Should you have questions/remarks, feel free to chime in !
On 28/10/2021 14:53, Fabian Arrotin wrote:
Hi all CI infra tenants/users,
As a follow-up wrt previous mail about cico-workspace container update (see https://lists.centos.org/pipermail/ci-users/2021-October/002184.html) we had a look at what was needed to rebase the cico-workspace container to CentOS 8-stream.
We've built a container that you can start using with the following specs: - based on centos 8-stream - so having python3 (instead of python2), important for your jobs - still providing python-cicoclient (python3 version) - ansible 2.9.27 - git
This container is actually available as staging tag, so it's not *yet* the one that is automatically pulled through your jenkins as "cloud/container" node to run your jobs.
We'd like you to start testing your jobs against that updated cico-workspace, at your earliest convenience, so that you have a chance to eventually adapt your jobs, or ask us to add/change something in that container.
See the next items
# How to test ? The current DeploymentConfig used in openshift will provide jenkins, itself configure to pull cico-workspace from quay.io (quay.io/centosci/cico-workspace:latest) But you can also , as you have full admin rights in your own jenkins namespace, temporary switch to :staging tag.
To proceed, just log into your own jenkins apps on openshift/ocp.ci and follow the next steps:
Manage Jenkins Manage Nodes and Clouds (under System Configuration) Configure Clouds (on the left menu) Expand Kubernetes and under Pod template you'll see "cico-workspace" "Pod Template details" Containers Just swap quay.io/centosci/cico-workspace:latest => quay.io/centosci/cico-workspace:staging Apply/Save
You can now test your job (test job) and see if that still works or if you need to adapt something
# How to revert ? Assuming that you want to revert to :latest test (still c7 based), just proceed as above and swap back to quay.io/centosci/cico-workspace:latest
#When will you enforce the change ?
We have no fixed date in mind but we'd like to enforce this early december, which would give you enough time to fix your jobs (if there is a need to). We can also provide an alternative through a different tag like :c7 while we'd have c8s for :latest and you'd then be also able to modify your jobs to just continue to use older c7 container (not adviced though, but we'll continue to rebuild the container for security updates automatically)
Should you have questions/remarks, feel free to chime in !
Quick reminder/follow-up on this : next week, on Thursday December 2nd, we'll make this new image the default, so all your cico-workspace pods in ocp.ci will be running from these refreshed images.
If you ignored previous mail asking for feedback, and that you have issue[s] with your ci scripts that were targeting centos 7/python 2, you'll be able to just use the previous container : Just follow the previous method but replace quay.io/centosci/cico-workspace:latest with quay.io/centosci/cico-workspace:cico-workspace-c7
Kind Regards,
On 23/11/2021 08:52, Fabian Arrotin wrote:
On 28/10/2021 14:53, Fabian Arrotin wrote:
Hi all CI infra tenants/users,
As a follow-up wrt previous mail about cico-workspace container update (see https://lists.centos.org/pipermail/ci-users/2021-October/002184.html) we had a look at what was needed to rebase the cico-workspace container to CentOS 8-stream.
We've built a container that you can start using with the following specs: - based on centos 8-stream - so having python3 (instead of python2), important for your jobs - still providing python-cicoclient (python3 version) - ansible 2.9.27 - git
This container is actually available as staging tag, so it's not *yet* the one that is automatically pulled through your jenkins as "cloud/container" node to run your jobs.
We'd like you to start testing your jobs against that updated cico-workspace, at your earliest convenience, so that you have a chance to eventually adapt your jobs, or ask us to add/change something in that container.
See the next items
# How to test ? The current DeploymentConfig used in openshift will provide jenkins, itself configure to pull cico-workspace from quay.io (quay.io/centosci/cico-workspace:latest) But you can also , as you have full admin rights in your own jenkins namespace, temporary switch to :staging tag.
To proceed, just log into your own jenkins apps on openshift/ocp.ci and follow the next steps:
Manage Jenkins Manage Nodes and Clouds (under System Configuration) Configure Clouds (on the left menu) Expand Kubernetes and under Pod template you'll see "cico-workspace" "Pod Template details" Containers Just swap quay.io/centosci/cico-workspace:latest => quay.io/centosci/cico-workspace:staging Apply/Save
You can now test your job (test job) and see if that still works or if you need to adapt something
# How to revert ? Assuming that you want to revert to :latest test (still c7 based), just proceed as above and swap back to quay.io/centosci/cico-workspace:latest
#When will you enforce the change ?
We have no fixed date in mind but we'd like to enforce this early december, which would give you enough time to fix your jobs (if there is a need to). We can also provide an alternative through a different tag like :c7 while we'd have c8s for :latest and you'd then be also able to modify your jobs to just continue to use older c7 container (not adviced though, but we'll continue to rebuild the container for security updates automatically)
Should you have questions/remarks, feel free to chime in !
Quick reminder/follow-up on this : next week, on Thursday December 2nd, we'll make this new image the default, so all your cico-workspace pods in ocp.ci will be running from these refreshed images.
If you ignored previous mail asking for feedback, and that you have issue[s] with your ci scripts that were targeting centos 7/python 2, you'll be able to just use the previous container : Just follow the previous method but replace quay.io/centosci/cico-workspace:latest with quay.io/centosci/cico-workspace:cico-workspace-c7
Kind Regards,
Just to let you know that it's now live, as announced.
Just to let you know that it's now live, as announced.
Many thanks Fabian :)
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab _______________________________________________ CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-
Fabian Arrotin -
Vipul Siddharth