Skip to content

Review quay_binaries_push workflow for oadp-1.6 branch support #153

@kaovilai

Description

@kaovilai

Note

Responses generated with Claude

Context

The oadp-1.6 branch is being set up for OADP 1.6 release. CI operator image configs have been added in openshift/release to build and mirror oadp-cli-oadp-1.6 images to quay.io/konveyor/oadp-cli-binaries.

Current behavior

The quay_binaries_push.yml workflow currently:

  • Triggers on v* tag pushes (and PRs for build-only)
  • Pushes multi-arch images to quay.io/konveyor/oadp-cli-binaries with the tag version and latest

Action items

Review whether any changes are needed for oadp-1.6 (and future release branches):

  • Should the workflow trigger on pushes to the oadp-1.6 branch (in addition to tags)?
  • Should branch pushes tag images differently (e.g., oadp-1.6 or oadp-1.6-latest instead of overwriting latest)?
  • Does the oadp-1.6 branch need to exist in this repo, or is oadp-dev sufficient as the development branch with tags for releases?
  • Any other workflow adjustments needed for the release process?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions