Skip to content

Add a notice for node e2e config files#54328

Merged
k8s-github-robot merged 1 commit intokubernetes:masterfrom
krzyzacy:node-notice
Oct 23, 2017
Merged

Add a notice for node e2e config files#54328
k8s-github-robot merged 1 commit intokubernetes:masterfrom
krzyzacy:node-notice

Conversation

@krzyzacy
Copy link
Copy Markdown
Member

ref #53542 and patched up with kubernetes/test-infra#5107

So while migrating the jobs to prow, I haven't kill the *.properties files yet because some lingering jobs, and possibly local tests are still using them. We have a copy of image-config.yaml in test-infra, and all *.properties file is merged into job configs.

Add a notice to remind people also update the job configs in test-infra. Also add myself as a reviewer here so I can subscribe some notice. I'll remove them once I cleaned up all legacy files here.

/assign @yguo0905 @dashpole @yujuhong

@k8s-ci-robot k8s-ci-robot added retest-not-required-docs-only size/S Denotes a PR that changes 10-29 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Oct 20, 2017
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

@krzyzacy: Adding do-not-merge/release-note-label-needed because the release note process has not been followed.

Details

One of the following labels is required "release-note", "release-note-action-required", or "release-note-none".
Please see: https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md#write-release-notes-if-needed.

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.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. label Oct 20, 2017
@krzyzacy
Copy link
Copy Markdown
Member Author

/release-note-none

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Oct 20, 2017
@krzyzacy
Copy link
Copy Markdown
Member Author

/kind e2e

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it help to add a approver section with a smaller set of approvers?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I only try to subscribe to some notifications when people are touching those config/property files so I added myself as a reviewer for now. If you think approves are better I can make the change :-)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As a reviewer, you'd get only a small number of PRs.

I think it makes sense to add an approver section, and put a couple of people who are aware of the situation there.

@krzyzacy
Copy link
Copy Markdown
Member Author

(okay, updated and github recovered from 🦄)

@yujuhong
Copy link
Copy Markdown
Contributor

/lgtm

@dashpole @Random-Liu @yguo0905 please ack for being added as an approver.

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 23, 2017
@dashpole
Copy link
Copy Markdown
Contributor

ack

@krzyzacy
Copy link
Copy Markdown
Member Author

/retest

@yujuhong
Copy link
Copy Markdown
Contributor

/approve no-issue

@k8s-github-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: krzyzacy, yujuhong

Associated issue requirement bypassed by: yujuhong

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

Details Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@k8s-github-robot k8s-github-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 23, 2017
@k8s-github-robot
Copy link
Copy Markdown

Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions here.

@k8s-github-robot k8s-github-robot merged commit 82a52a9 into kubernetes:master Oct 23, 2017
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants