Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Automated docker validation tests #22765

Closed
dchen1107 opened this issue Mar 10, 2016 · 6 comments
Closed

Automated docker validation tests #22765

dchen1107 opened this issue Mar 10, 2016 · 6 comments
Assignees
@Random-Liu
Labels
area/test lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.
Milestone
next-candidate

Comments

@dchen1107
Copy link
Member

dchen1107 commented Mar 10, 2016 •
edited
Loading

We introduced node test infrastructure for 1.2 release, and engineers are working on docker validation test suite too. We should automate today's docker release validation process by fetching the latest docker release candidate from docker.io and run our node conformance tests.

cc/ @kubernetes/goog-node
@dchen1107 dchen1107 added area/test priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node. labels Mar 10, 2016
@dchen1107 dchen1107 added this to the next-candidate milestone Mar 10, 2016
@dchen1107
Copy link
Member Author

@liangchenye I am assigning this one to you for now. Please let us know if you don't have the bandwidth for this.

@liangchenye
Copy link
Contributor

@dchen1107 I have 1/3 of my working hour on this between March and April. I'll update my progress by submit PRs.

@dchen1107
Copy link
Member Author

@liangchenye Could you delegate this to one of your co-workers since I don't have their github names? Thanks!

@liangchenye
Copy link
Contributor

@dchen1107, I'll catch up with the 'docker unique test' this week and see if it is necesary to delegate to other co-workers.

@Random-Liu
Copy link
Member

Also ref #21013

@timstclair timstclair mentioned this issue Mar 23, 2016
Closed
5 tasks
@aronchick aronchick mentioned this issue Aug 25, 2016
Closed
16 tasks
@Random-Liu Random-Liu mentioned this issue Sep 2, 2016
Merged
@fejta-bot
Copy link

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 17, 2017
openshift-publish-robot pushed a commit to openshift/kubernetes that referenced this issue May 4, 2019
@k8s-publishing-bot
Merge pull request kubernetes#22765 from deads2k/sally-rbr
a9532d9 
add RBR from CRDs

Origin-commit: a0a3b1f6f90faae6f960030136b54aa5800369cf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Random-Liu Random-Liu

Labels
area/test lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Milestone
next-candidate
Development

No branches or pull requests
6 participants
@Random-Liu @dchen1107 @yujuhong @liangchenye @k8s-ci-robot @fejta-bot