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

[Umbrella] Repo improvements #266

Closed
26 tasks done
justaugustus opened this issue Oct 16, 2020 · 11 comments · Fixed by kubernetes/test-infra#23598
Closed
26 tasks done

[Umbrella] Repo improvements #266

justaugustus opened this issue Oct 16, 2020 · 11 comments · Fixed by kubernetes/test-infra#23598
Assignees
@justaugustus
Labels
sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@justaugustus
Copy link
Member

justaugustus commented Oct 16, 2020 •
edited
Loading

This a braindump of tasks I've done / plan on doing to improve the repo...

/sig release
/area release-eng
/wg k8s-infra

cc: @kubernetes-sigs/release-engineering
@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. wg/k8s-infra labels Oct 16, 2020
@k8s-ci-robot
Copy link
Contributor

@justaugustus: The label(s) area/release-eng cannot be applied, because the repository doesn't have them

In response to this:

This a braindump of tasks I've done / plan on doing to improve the repo...

  • Code organization
  • (go: Init submodules for lib/ and pkg/ #261) Init submodules, so libraries are importable
  • (Init v2 module #260) Init v2 module (needs bazel cleanup first)
  • (Migrate lib/ packages into pkg/ #262) Migrate lib/ into pkg/
  • (Consolidate packages (part two) #263) Migrate vulnerability dashboard library into pkg/
  • OWNERS
  • (Update OWNERS #265) Establish Release Engineering ownership of repo
  • (Update OWNERS #265) Add active maintainers / prune inactive
  • Enable OWNERS to perform image promotion
  • Update SIG Release teams to include current CIP maintainers
  • Test Infra / Contributing
  • Update RelEng ownership of CI jobs & inform Release Managers of CI failures
  • Add issue/PR templates
  • Add RelEng labels to repo
  • Enable common prow plugins
  • CLI tool migration
  • Migrate promobot (promobot-files, promobot-generate-manifest) tools to k/release
    • Create Dockerfiles for promobot tools
    • Integrate file promotion into k/k release process
  • (Maybe) Migrate cip-mm to k/release

/sig release
/area release-eng
/wg k8s-infra

cc: @kubernetes-sigs/release-engineering

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.

@justaugustus
Copy link
Member Author

/assign

This was referenced Oct 16, 2020
Merged
Merged
@cpanato
Copy link
Member

cpanato commented Oct 16, 2020

I will work on the Test Infra / Contributing items

This was referenced Oct 16, 2020
Merged
Merged
Merged
Merged
Merged
@spiffxp
Copy link
Member

spiffxp commented Oct 16, 2020

Suggestion for test-infra changes: container-image-promoter jobs that currently run in the google.com-owned prow.k8s.io service cluster should run in community-owned infrastructure instead

Migrating to k8s-infra-prow-build-trusted would involve:

@spiffxp spiffxp mentioned this issue Oct 16, 2020
Closed
@justaugustus justaugustus mentioned this issue Oct 17, 2020
Closed
8 tasks
@justaugustus justaugustus changed the title Repo improvements [Umbrella] Repo improvements Oct 17, 2020
@justaugustus
Copy link
Member Author

Suggestion for test-infra changes: container-image-promoter jobs that currently run in the google.com-owned prow.k8s.io service cluster should run in community-owned infrastructure instead

Thanks for all of the details, @spiffxp!
I've opened #269 to track this, since it's a bit meaty compared to the other tasks in this umbrella.

This was referenced Oct 20, 2020
Merged
Merged
Merged
@listx listx mentioned this issue Oct 23, 2020
Closed
This was referenced Oct 26, 2020
Merged
Merged
This was referenced Nov 21, 2020
Merged
Merged
@fejta-bot
Copy link

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

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

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 Apr 11, 2021
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 11, 2021
@listx
Copy link
Contributor

listx commented May 25, 2021

/remove-lifecycle rotten
/cc @tylerferrara

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label May 25, 2021
@justaugustus justaugustus mentioned this issue May 26, 2021
Closed
This was referenced May 27, 2021
Closed
Merged
This was referenced May 30, 2021
Merged
Merged
@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 Sep 8, 2021
@justaugustus justaugustus removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 8, 2021
This was referenced Sep 14, 2021
Closed
Merged
@justaugustus
Copy link
Member Author

To keep this from being open indefinitely...

Recently merged:

Moved to a separate issue:

Closed with:

/close

@k8s-ci-robot
Copy link
Contributor

@justaugustus: Closing this issue.

In response to this:

To keep this from being open indefinitely...

Recently merged:

Moved to a separate issue:

Closed with:

/close

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

@justaugustus justaugustus

Labels
sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

releng(promo-tools): Update OWNERS for presubmits justaugustus/test-infra
7 participants
@spiffxp @justaugustus @listx @cpanato @k8s-ci-robot @fejta-bot @k8s-triage-robot