Blame docs/operations/ci/upgrades/cico-workspace-container.md

1843bb
# cico-workspace container upgrade
1843bb
1843bb
## Overview
1843bb
1843bb
We provide a [template](https://github.com/centosci/images/blob/master/cico-workspace/openshift/templates/centosci-workspace.yml) that is used to pre-deploy dedicated jenkins pod in our openshift setup.
1843bb
It's using jenkins container maintained by Red Hat (RH catalog) and also a specific jenkins-agent container (called cico-workspace) that is spun up for each job that should run in that jenkins environment (dedicated per project/tenant in CI ocp infra)
1843bb
1843bb
All that is also discussed in the "Onboard Tenants" section.
1843bb
1843bb
## Updating cico-workspace image
1843bb
1843bb
The `cico-workspace` container image is available in dedicated [Quay.io](https://quay.io/repository/centosci/cico-workspace) repository.
1843bb
That's the repositry/registry that ocp.ci cluster is using to spin up cico-workspace containers on demand, always verifying if there is a new one and then pulling :
1843bb
1843bb
```xml
1843bb
  <image>quay.io/centosci/cico-workspace:latest</image>
1843bb
  <privileged>false</privileged>
1843bb
  <alwaysPullImage>true</alwaysPullImage>
1843bb
```
1843bb
1843bb
The container (re)build process happens either through :
1843bb
1843bb
  * git commit/push in upstream [git repository](https://github.com/centosci/images)
1843bb
  * a manual build trigger in quay.io
1843bb
1843bb
Some notes about what we provide in that cico-workspace image :
1843bb
1843bb
  * centos 7 updated container with jenkins agent (java)
1843bb
  * ansible (from our own configmanagement SIG)
1843bb
  * [python-cicoclient](https://github.com/CentOS/python-cicoclient/) rpm built through cbs.centos.org koji, and needed to interact easily with Duffy API when requesting  a node to run tests on