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

Cleanup e2e_node/jenkins #92674

Closed
alejandrox1 opened this issue Jul 1, 2020 · 23 comments
Closed

Cleanup e2e_node/jenkins #92674

alejandrox1 opened this issue Jul 1, 2020 · 23 comments
Assignees
@Kappie37
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@alejandrox1
Copy link
Contributor

There are some leftover test artifacts from the time when e2e tests were executed with Jenkins.
The artifacts can be found here https://github.com/kubernetes/kubernetes/tree/master/test/e2e_node/jenkins

We should look into these files and see

  • what do we need to move elsewhere?
  • what needs to be updated?
  • what can we delete?

/help wanted
/good-first-issue
/sig node
@alejandrox1 alejandrox1 added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 1, 2020
@k8s-ci-robot
Copy link
Contributor

@alejandrox1:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

There are some leftover test artifacts from the time when e2e tests were executed with Jenkins.
The artifacts can be found here https://github.com/kubernetes/kubernetes/tree/master/test/e2e_node/jenkins

We should look into these files and see

  • what do we need to move elsewhere?
  • what needs to be updated?
  • what can we delete?

/help wanted
/good-first-issue
/sig node

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 sig/node Categorizes an issue or PR as relevant to SIG Node. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jul 1, 2020
@alejandrox1
Copy link
Contributor Author

/kind cleanup
/remove-kind feature

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. and removed kind/feature Categorizes issue or PR as related to a new feature. labels Jul 1, 2020
@mayankshah1607
Copy link

@alejandrox1 I'd like to give this a try!

@mayankshah1607
Copy link

/assign

@alejandrox1
Copy link
Contributor Author

Thank you @mayankshah1607
Please reach out if you have any questions. I'll also will swing by to see how things are going 😄

@alejandrox1
Copy link
Contributor Author

/remove-help wanted

@alejandrox1
Copy link
Contributor Author

Hi @mayankshah1607 , wanted to ping you on this again to check how things are going.
Do you need any help?

@mayankshah1607
Copy link

mayankshah1607 commented Aug 4, 2020 •
edited
Loading

Hi @alejandrox1
Should we be moving the gci-init.yaml and cos-init-live-restore.yaml files to test-infra/jobs/e2e_node? I see that they're being used for various configs in test-infra/jobs/e2e_node.
It also seems like we can delete docker_validation/ (it is being handled in test-infra/jobs/e2e_node/benchmark_config.yaml) and conformance/

@leilajal
Copy link
Contributor

@mayankshah1607 Hi I'm interested to know the status of this

@SergeyKanzhelev
Copy link
Member

/uncc @mayankshah1607

@piyushsingariya
Copy link

@mayankshah1607 Any updates over this? I'm interested in working on this??

@mayankshah1607
Copy link

@piyushsingariya Please feel free to take this up! :)

@mayankshah1607 mayankshah1607 removed their assignment Dec 29, 2020
@Aut0R3V
Copy link

Aut0R3V commented Jan 6, 2021

Hey this looks intresting, I can take this up if no one's working on it

@Kappie37
Copy link

/assign

@Kappie37
Copy link

Right now, I speak for a group of students from Delft University of Technology. As part of a course, we want to contribute to Kubernetes. This issue seemed like a good start. Is there any more information we can use to fix this issue?

@Kappie37
Copy link

Dear @alejandrox1 @krzyzacy,

We were looking at this issue and observed that in test-infra (https://github.com/kubernetes/test-infra/tree/master/jenkins) Jenkins is dead. Why can we not delete these remaining test artifacts from the time when e2e tests were executed with Jenkins? If it is not possible/wise to delete, how can we figure out what needs to be preserved?

Do you need us to rewrite the Jenkins tests into the Prow CI/CD system?

@Kappie37 Kappie37 mentioned this issue Mar 1, 2021
Closed
@Kappie37 Kappie37 removed their assignment May 7, 2021
@SergeyKanzhelev
Copy link
Member

/assign @Kappie37

(since you sent the PR)

@wgahnagl wgahnagl mentioned this issue Jun 24, 2021
Open
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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 Aug 10, 2021
@pacoxu
Copy link
Member

pacoxu commented Aug 20, 2021

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 20, 2021
@SaNsK11
Copy link

SaNsK11 commented Aug 26, 2021

@alejandrox1 is someone working on it...can i help in some way?

@pacoxu
Copy link
Member

pacoxu commented Sep 1, 2021

@alejandrox1 is someone working on it...can i help in some way?

@SaNsK11 #99606 is the PR to fix this issue.

@SergeyKanzhelev
Copy link
Member

/close

in favor of #106119 which @endocrimes self-assigned.

@k8s-ci-robot
Copy link
Contributor

@SergeyKanzhelev: Closing this issue.

In response to this:

/close

in favor of #106119 which @endocrimes self-assigned.

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
Assignees

@Kappie37 Kappie37

Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
SIG Node CI/Test Board
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove deprecated/dead Jenkins e2e_node tests