Allow a dev-scripts PR to test configuration change

[andfasano]

This PR is meant to provide support for testing a PR that requires a dev-scripts configuration change. Currently this is not possible, and this means that every time a developer proposes a PR for dev-scripts repo containing new code activated by a configuration change the CI does not exercise it.

With this PR, a developer can now temporarily add the dev-scripts-additional-config file in his/her own PR with the required configuration settings and test it.

[stbenjam]

Usually I just dump the new config into common.sh or something, this seems a bit nicer.

[andfasano]

/test pj-rehearse

[andfasano]

/test pj-rehearse

[andfasano]

Usually I just dump the new config into common.sh or something, this seems a bit nicer.

This change could help PRs like openshift-metal3/dev-scripts#1084

[andfasano]

/test pj-rehearse

[stbenjam]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andfasano, stbenjam

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/step-registry/baremetalds/devscripts/setup/OWNERS [andfasano,stbenjam]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@andfasano: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/rehearse/openshift-metal3/dev-scripts/master/e2e-metal-ipi-dualstack	acb9175	link	/test pj-rehearse
ci/prow/pj-rehearse	acb9175	link	/test pj-rehearse

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

[andfasano]

/test core-valid

[openshift-ci-robot]

@andfasano: Updated the following 2 configmaps:

• step-registry configmap in namespace ci at cluster api.ci using the following files:
  • key baremetalds-devscripts-setup-commands.sh using file ci-operator/step-registry/baremetalds/devscripts/setup/baremetalds-devscripts-setup-commands.sh
• step-registry configmap in namespace ci at cluster app.ci using the following files:
  • key baremetalds-devscripts-setup-commands.sh using file ci-operator/step-registry/baremetalds/devscripts/setup/baremetalds-devscripts-setup-commands.sh

Details

In response to this:

This PR is meant to provide support for testing a PR that requires a dev-scripts configuration change. Currently this is not possible, and this means that every time a developer proposes a PR for dev-scripts repo containing new code activated by a configuration change the CI does not exercise it.

With this PR, a developer can now temporarily add the dev-scripts-additional-config file in his/her own PR with the required configuration settings and test it.

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.