openshift / openshift/oadp-operator

e2e detects prow and use images from ci-registry to eliminate mirror delays

Open
#1,569 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/feature lifecycle/frozen testing
Dominant language
Go
Stars
92
Forks
93
Avg merge
1d 23h
Merged PRs (30d)
43

Description

Is your feature request related to a problem? Please describe.

See ci registry format in https://github.com/openshift/oadp-operator/issues/1233
Describe the solution you'd like

Describe alternatives you've considered

Additional context

unblocks usage with https://docs.ci.openshift.org/docs/how-tos/multi-pr-presubmit-testing/
and removes 1h mirror delay required to test latest changes from plugin repos.

Enhancement we had requested with multi-pr presubmit tests https://issues.redhat.com/browse/DPTP-4224 which were eventually closed cause we did not respond.

Another idea is to extend following substitutions list to include plugins
operator:
  bundles:
  - dockerfile_path: build/Dockerfile.bundle
  substitutions:
  - pullspec: quay.io/konveyor/oadp-operator:oadp-1.5
    with: oadp-operator-1.5

but it would require Containerfile in this repo for each plugin and produce "untested" images.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by tracing the repository's e2e and Prow presubmit configuration, then review the ci-registry format referenced in issue 1233 and the substitutions example. Done means Prow is detected, plugin images can use ci-registry images, and the one-hour mirror delay is removed for multi-PR presubmit testing.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
build-system, ci-cd, devops, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.