From 0910436e67bba7433b82ee9fc2d44d43d23c38b5 Mon Sep 17 00:00:00 2001 From: Adam Toy Date: Wed, 26 Apr 2023 09:26:23 -0400 Subject: [PATCH] Add image release cadence (#76) Co-authored-by: Adam Toy --- docs/registry-docs/release-cadence.md | 11 +++++++++++ sidebars.js | 1 + 2 files changed, 12 insertions(+) create mode 100644 docs/registry-docs/release-cadence.md diff --git a/docs/registry-docs/release-cadence.md b/docs/registry-docs/release-cadence.md new file mode 100644 index 0000000..3a26c9a --- /dev/null +++ b/docs/registry-docs/release-cadence.md @@ -0,0 +1,11 @@ +# Release Cadence + +This page will walk through how the pipelines are currently configured to execute, and future plans. + +## Pipelines (Current) + +Currently, pipelines against the Rancher product portfolio execute nightly. That means that, if a new release of a Rancher product occurs, it will be available through Carbide the next day. + +## Pipelines (Future) + +We are actively working towards a reactive approach to our pipelines, and should soon support our pipelines triggering directly after a release of a Rancher product occurs. Given the pipelines will take time to process, this will mean the images will be available in a matter of minutes/hours after the upstream release, depending on the number of images for the product. \ No newline at end of file diff --git a/sidebars.js b/sidebars.js index 4d647d4..6bc5c0f 100644 --- a/sidebars.js +++ b/sidebars.js @@ -70,6 +70,7 @@ const sidebars = { ], }, 'registry-docs/architecture', + 'registry-docs/release-cadence', ], }, {