Our pipeline currently produces two RPM packages and publishes them to services such as PackageCloud and Cloudsmith. However, a manually triggered separate job is what creates the tag and GitHub release. Now that we have over a year of
evidence that our patches do not go stale very often and for almost all releases, patching succeeds, we should fully automate this process.
This depends on addressing #92 one way or another.
Our pipeline currently produces two RPM packages and publishes them to services such as PackageCloud and Cloudsmith. However, a manually triggered separate job is what creates the tag and GitHub release. Now that we have over a year of evidence that our patches do not go stale very often and for almost all releases, patching succeeds, we should fully automate this process.
This depends on addressing #92 one way or another.