Skip to content

Conversation

@cybertron
Copy link
Member

The coredns-mdns project is vendored into coredns, and since that
has a significant impact on baremetal deployments we want to be able
to run ci on coredns PRs.

@cybertron
Copy link
Member Author

/retest

I didn't touch most of the failing tests, and the one I did add failed on an unrelated issue.

@cybertron
Copy link
Member Author

/test pj-rehearse

@cybertron cybertron force-pushed the coredns-metal-ci branch 2 times, most recently from 58cf907 to 83e549e Compare July 9, 2020 21:26
@cybertron
Copy link
Member Author

/test pj-rehearse

1 similar comment
@cybertron
Copy link
Member Author

/test pj-rehearse

@cybertron
Copy link
Member Author

/assign @danehans

The new jobs that I added are all passing, so I think this is good to go.

The coredns-mdns project is vendored into coredns, and since that
has a significant impact on baremetal deployments we want to be able
to run ci on coredns PRs.
@sgreene570
Copy link

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 21, 2020
@Miciah
Copy link
Contributor

Miciah commented Sep 21, 2020

/lgtm

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cybertron, Miciah, sgreene570

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:

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 openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 21, 2020
@openshift-merge-robot openshift-merge-robot merged commit 6639ae5 into openshift:master Sep 21, 2020
@openshift-ci-robot
Copy link
Contributor

@cybertron: Updated the following 9 configmaps:

  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-coredns-master.yaml using file ci-operator/config/openshift/coredns/openshift-coredns-master.yaml
  • ci-operator-4.4-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-coredns-release-4.4.yaml using file ci-operator/config/openshift/coredns/openshift-coredns-release-4.4.yaml
  • ci-operator-4.5-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-coredns-release-4.5.yaml using file ci-operator/config/openshift/coredns/openshift-coredns-release-4.5.yaml
  • job-config-master configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-coredns-master-presubmits.yaml using file ci-operator/jobs/openshift/coredns/openshift-coredns-master-presubmits.yaml
  • job-config-4.4 configmap in namespace ci at cluster api.ci using the following files:
    • key openshift-coredns-release-4.4-presubmits.yaml using file ci-operator/jobs/openshift/coredns/openshift-coredns-release-4.4-presubmits.yaml
  • job-config-4.5 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-coredns-release-4.5-presubmits.yaml using file ci-operator/jobs/openshift/coredns/openshift-coredns-release-4.5-presubmits.yaml
  • job-config-master configmap in namespace ci at cluster api.ci using the following files:
    • key openshift-coredns-master-presubmits.yaml using file ci-operator/jobs/openshift/coredns/openshift-coredns-master-presubmits.yaml
  • job-config-4.4 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-coredns-release-4.4-presubmits.yaml using file ci-operator/jobs/openshift/coredns/openshift-coredns-release-4.4-presubmits.yaml
  • job-config-4.5 configmap in namespace ci at cluster api.ci using the following files:
    • key openshift-coredns-release-4.5-presubmits.yaml using file ci-operator/jobs/openshift/coredns/openshift-coredns-release-4.5-presubmits.yaml
Details

In response to this:

The coredns-mdns project is vendored into coredns, and since that
has a significant impact on baremetal deployments we want to be able
to run ci on coredns PRs.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants