CI/CD

August 25, 2021

/pulp/api/v3/
- https://github.com/pulp/plugin_template/pull/477/files#r695716549
Meetings
- Lack of topics
- Cancel standing regular meeting
- Schedule again if needed

Remember to build the oci-images even for bugfix releases
- Add to release guide - https://github.com/pulp/community/wiki/Release-Guide
- start a discussion https://github.com/pulp/pulp-oci-images/issues/109#issuecomment-886815529
  [mdellweg]
should we provide a pulp_ci_base:3.14 for all builds (and later releases) with pulpcore 3.14.z?
[mdellweg] file an issue and ask for feedback
Operator needs support for db encryption key
- https://pulp.plan.io/issues/8730
- [fao] will work on that
SSL images merged
- just a matter of enabling it on every plugin
- pulp-ansible done!
- https://github.com/pulp/pulp_container/pull/304
- https://github.com/pulp/pulpcore/pull/1522
pulpbot needs workflows permission for update-ci job
Fix branch permissions on pulp-oci-images
- [davidd]
pulpbot can't push new images e.g. molecule_debian11

HTTPS tests blocked by: https://github.com/pulp/pulp-oci-images/pull/84
- Switch http/https at runtime - example: https://hub.docker.com/r/plexinc/pms-docker/
Revisit release automation issues in redmine
- https://pulp.plan.io/issues/8093
- What can be closed out? What can be moved?
Python 3.8 in containers https://github.com/pulp/pulp-oci-images/pull/103

Upgrade tests
- done!
HTTPS tests
- started Makefile + Template PR
- https://github.com/pulp/pulp-oci-images/pull/84
- blocked by pulp-ansible 0.8.0 release but it is ready for review
Release automation
- requirements are not being read - https://github.com/pulp/pulp_maven/pull/41#issuecomment-851514599
[fao] - I have a meeting conflict

Upgrade tests
- merged
- addressing minor issues - https://github.com/pulp/plugin_template/pull/388
https tests
- working on https://github.com/pulp/pulp-oci-images/pull/73 to use template to build images
- for dynamically use tags (latest/http/https)
click upgrade is breaking (almost) everything
- current master branch of pulpcore and plugins are ok
- we may face issues with older pulpcore releases e.g. pulp_galaxy_image https://github.com/pulp/pulp-oci-images/pull/83/checks?check_run_id=2600446352#step:5:107
Release automation
- https://hackmd.io/VJtEmOqmTtCG6nujCvdTpA

Moving plugin_template to github issues?
- https://listman.redhat.com/archives/pulp-dev/2021-April/msg00019.html
pulp-oci-image changes not updating redmine
- Enable github/redmine integration
- Or track issues on github?
Releasing pulp_installer is tedious/cumbersome
- Automate building/publishing the collection?
  - https://dev.to/imjoseangel/release-and-deploy-ansible-collection-with-github-actions-4a62
  - Already done. Need to add a note to the release doc that it's only needed for older branches.
  - Can run "make dist" to build the collection
New workers in the CI
- https://github.com/pulp/pulp-oci-images/pull/71
Checked failing CI jobs

Github Actions
- good overall
  - faster and more reliable so far than Travis
  - easier to debug with tmate action
- downsides
  - virtualization
  - not possible to re-run individual jobs
    - https://github.com/actions/runner/issues/432
  - people need write permission to re-run CI
    - https://github.com/actions/runner/issues/841
    - workaround: git commit --amend, no changes, force push
Release automation https://pulp.plan.io/issues/8093
- Availability
  - Mike after operator?
  - David has ~1 FTE
  - Fabricio? Not sure. Maybe 0.5 FTE.
  - Dkliban?
- First goal? https://pulp.plan.io/issues/7868
  - [david] to write up design
Regular CI/CD meeting?
- Every other Wednesday 9:30-9:55am (15:30 EST)
- [david] to schedule
Convert CI/CD code to ansible playbook?
- Benefits: idempotence, easier to run locally
- Big rewrite