Closed lentzi90 closed 2 weeks ago
@lentzi90: The following test failed, say
/retest
to rerun all failed tests or/retest-required
to rerun all mandatory failed tests: Test name Commit Details Required Rerun command check-prow-config 3d2c8c9 link true/test check-prow-config
This fails because I have not updated the in-cluster config yet. It is trying to look for the config in its old place.
Thanks for the suggestion @tuminoid ! It is definitely doable if I understood you correctly, and I think I have a working solution now. What do you think?
Thanks for the suggestion @tuminoid ! It is definitely doable if I understood you correctly, and I think I have a working solution now. What do you think?
I need to take better look, but yes, that was what I was suggesting. Thanks!
/remove lgtm
/lgtm cancel
/remove-lgtm
/override check-prow-config
@Rozzii: Overrode contexts on behalf of Rozzii: check-prow-config
/hold
(Putting hold so I can apply the changes and check the test before it merges)
/test check-prow-config
/hold cancel The test passes now that I have applied the change
/override metal3-ubuntu-e2e-integration-test-main
@lentzi90: Overrode contexts on behalf of lentzi90: metal3-ubuntu-e2e-integration-test-main
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: tuminoid
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@lentzi90: Updated the following 4 configmaps:
plugins
configmap in namespace prow
at cluster default
using the following files:
plugins.yaml
using file ``plugins.yaml
using file prow/config/plugins.yaml
config
configmap in namespace prow
at cluster default
using the following files:
config.yaml
using file prow/config/config.yaml
job-config
configmap in namespace prow
at cluster default
using the following files:
metal3-clusterapi-docs.yaml
using file prow/config/jobs/Nordix/metal3-clusterapi-docs.yaml
metal3-dev-tools.yaml
using file prow/config/jobs/Nordix/metal3-dev-tools.yaml
sles-ironic-python-agent-builder.yaml
using file prow/config/jobs/Nordix/sles-ironic-python-agent-builder.yaml
baremetal-operator-release-0.5.yaml
using file prow/config/jobs/metal3-io/baremetal-operator-release-0.5.yaml
baremetal-operator-release-0.6.yaml
using file prow/config/jobs/metal3-io/baremetal-operator-release-0.6.yaml
baremetal-operator-release-0.8.yaml
using file prow/config/jobs/metal3-io/baremetal-operator-release-0.8.yaml
baremetal-operator.yaml
using file prow/config/jobs/metal3-io/baremetal-operator.yaml
cluster-api-provider-metal3.yaml
using file prow/config/jobs/metal3-io/cluster-api-provider-metal3.yaml
cluster-api-provier-metal3-release-1.6.yaml
using file prow/config/jobs/metal3-io/cluster-api-provier-metal3-release-1.6.yaml
cluster-api-provier-metal3-release-1.7.yaml
using file prow/config/jobs/metal3-io/cluster-api-provier-metal3-release-1.7.yaml
cluster-api-provier-metal3-release-1.8.yaml
using file prow/config/jobs/metal3-io/cluster-api-provier-metal3-release-1.8.yaml
community.yaml
using file prow/config/jobs/metal3-io/community.yaml
ip-address-manager-release-1.6.yaml
using file prow/config/jobs/metal3-io/ip-address-manager-release-1.6.yaml
ip-address-manager-release-1.7.yaml
using file prow/config/jobs/metal3-io/ip-address-manager-release-1.7.yaml
ip-address-manager-release-1.8.yaml
using file prow/config/jobs/metal3-io/ip-address-manager-release-1.8.yaml
ip-address-manager.yaml
using file prow/config/jobs/metal3-io/ip-address-manager.yaml
ironic-client.yaml
using file prow/config/jobs/metal3-io/ironic-client.yaml
ironic-hardware-inventory-recorder-image.yaml
using file prow/config/jobs/metal3-io/ironic-hardware-inventory-recorder-image.yaml
ironic-image-release-24.0.yaml
using file prow/config/jobs/metal3-io/ironic-image-release-24.0.yaml
ironic-image-release-24.1.yaml
using file prow/config/jobs/metal3-io/ironic-image-release-24.1.yaml
ironic-image-release-25.0.yaml
using file prow/config/jobs/metal3-io/ironic-image-release-25.0.yaml
ironic-image-release-26.0.yaml
using file prow/config/jobs/metal3-io/ironic-image-release-26.0.yaml
ironic-image.yaml
using file prow/config/jobs/metal3-io/ironic-image.yaml
ironic-ipa-downloader.yaml
using file prow/config/jobs/metal3-io/ironic-ipa-downloader.yaml
ironic-standalone-operator.yaml
using file prow/config/jobs/metal3-io/ironic-standalone-operator.yaml
mariadb-image.yaml
using file prow/config/jobs/metal3-io/mariadb-image.yaml
metal3-dev-env.yaml
using file prow/config/jobs/metal3-io/metal3-dev-env.yaml
metal3-docs.yaml
using file prow/config/jobs/metal3-io/metal3-docs.yaml
metal3-io.github.io.yaml
using file prow/config/jobs/metal3-io/metal3-io.github.io.yaml
project-infra.yaml
using file prow/config/jobs/metal3-io/project-infra.yaml
utility-images.yaml
using file prow/config/jobs/metal3-io/utility-images.yaml
periodics.yaml
using file prow/config/jobs/periodics.yaml
label-config
configmap in namespace prow
at cluster default
using the following files:
labels.yaml
using file ``labels.yaml
using file prow/config/labels.yaml
This moves all prow config to one folder outside of the kustomization and splits the jobs into multiple files. Kustomize cannot automatically create configmaps from all files in a folder recursively so I think it makes more sense to handle the config separately. Then we can also keep them in a place that is perhaps easier to find. This also paves the way for eventually separating out the secrets from the kustomization so that we can have a job for applying changes across all the manifests (not just the config).
The jobs are now in one file per repo. We can change this to one folder per repo or something else if we want.
Fixes: #713