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

Run the prod publishing-bot as a periodic job #353

Open
nikhita opened this issue May 24, 2023 · 14 comments
Open

Run the prod publishing-bot as a periodic job #353

nikhita opened this issue May 24, 2023 · 14 comments
Assignees
@akhilerm
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@nikhita
Copy link
Member

nikhita commented May 24, 2023

kubernetes/test-infra#29118 added a presubmit to run a dry-run of the bot.

We should do something similar to create a periodic job to run the prod bot. That will allow us to have testgrid integrations, easy access to logs and a multitude of other benefits.
@akhilerm
Copy link
Member

/assign

@ameukam
Copy link
Member

ameukam commented May 24, 2023

we will need at least:

  • a Github token
  • a dedicated volume in the build cluster or a ephemeral one on each run.

@akhilerm
Copy link
Member

@ameukam Is it possible to get a persistent volume on the build cluster ?

@ameukam
Copy link
Member

ameukam commented Jun 28, 2023

@akhilerm Yes. I'll work on that this week. Any suggestion about size for the PV ? we can start with 50 GB ?

@akhilerm
Copy link
Member

yep. that would work. The current production instance uses 100Gi volume as mentioned in https://github.com/kubernetes/publishing-bot/blob/master/artifacts/manifests/pvc.yaml#L4

@akhilerm
Copy link
Member

@ameukam Gentle reminder to look into this issue for getting PV in test infra

ameukam added a commit to ameukam/k8s.io that referenced this issue Aug 4, 2023
@ameukam
prow-build-trusted: Add PVC for publishing-bot
3a568f3 
Related to:
  - kubernetes/publishing-bot#353

Add a PVC that will be used publishing-bot as a prowjob

Signed-off-by: Arnaud Meukam <[email protected]>
@ameukam ameukam mentioned this issue Aug 4, 2023
Merged
@sayanchowdhury
Copy link
Member

we will need at least:

  • a Github token
  • a dedicated volume in the build cluster or a ephemeral one on each run.

@ameukam we would also need new secret with a Github token in the k8s.io, right? Should I file a PR for that in the k8s.io repo?

This was referenced Aug 30, 2023
Closed
Closed
ameukam added a commit to ameukam/k8s.io that referenced this issue Oct 10, 2023
@ameukam
Add a github token for publishing-bot
1a56184 
Related to:
  - kubernetes/publishing-bot#353

Sync existing Github token to trusted GKE cluster `prow-build-trusted`.
The token will be consumed by a prowjob

Signed-off-by: Arnaud Meukam <[email protected]>
This was referenced Oct 10, 2023
Merged
Merged
@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue 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 Jan 26, 2024
@ameukam
Copy link
Member

ameukam commented Jan 26, 2024

/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 Jan 26, 2024
@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue 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 Apr 25, 2024
@akhilerm
Copy link
Member

akhilerm commented May 1, 2024

/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 May 1, 2024
@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue 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 Jul 30, 2024
@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please 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 Aug 29, 2024
@akhilerm
Copy link
Member

/lifecycle frozen

@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 Aug 30, 2024
@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@akhilerm akhilerm

Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add periodic job for the publishing bot sayanchowdhury/test-infra
6 participants
@sayanchowdhury @ameukam @akhilerm @nikhita @k8s-ci-robot @k8s-triage-robot