Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-4760

Simplify and automate image-updater release process

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • 8
    • GitOps Tangerine - Sprint 3256, GitOps Tangerine - Sprint 3258

      Story (Required)

      As a project maintainer trying to release a new version I want to simplify and automate the release process

      Currently image-updater project release is done manually with a script. We should be able to automate it using mechanisms like github actions.  For reference, see argo-cd project releasing docs: argo-cd/docs/developer-guide/releasing.md

      upstream issue: Automate the release process with github actions workflow · Issue #734 · argoproj-labs/argocd-image-updater

      Background (Required)

      <Describes the context or background related to this story>

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      <Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

      Dependencies

      <Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

      Acceptance Criteria (Mandatory)

      • the release process is automated
      • the new automated release process should support all the steps as in the current script.
      • communicate with the argocd-image-updater community about the automated release process

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              cfang@redhat.com Cheng Fang
              cfang@redhat.com Cheng Fang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: