Introduce the .ci-operator.yaml file #183
Conversation
Allows us to control the build_root ci-operator configuration for o/operator-framework-olm in the repository vs. in o/release. This allows us to make changes to the build root Dockerfile (base.Dockerfile) and have those changes get tested in the same PR. Previously, the build root Dockerfile was always built using the HEAD version, which led to situations where you would need to first merge (blindly) to master, then open a PR to test those changes worked.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: timflannagan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
This doesn't affect e2e tests. /override ci/prow/e2e-aws-olm |
|
@timflannagan: Overrode contexts on behalf of timflannagan: ci/prow/e2e-aws-olm, ci/prow/e2e-upgrade In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Allows us to control the build_root ci-operator configuration for
o/operator-framework-olm in the repository vs. in o/release. This allows
us to make changes to the build root Dockerfile (base.Dockerfile) and
have those changes get tested in the same PR. Previously, the build root
Dockerfile was always built using the HEAD version, which led to
situations where you would need to first merge (blindly) to master, then
open a PR to test those changes worked.