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.

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

Investigate lifecycle stale and rotten etc #1492

Open
tomhobson opened this issue Oct 5, 2022 · 2 comments
Open

Investigate lifecycle stale and rotten etc #1492

tomhobson opened this issue Oct 5, 2022 · 2 comments

Comments

@tomhobson
Copy link
Member

This was working in 2021, but we need to investigate how and where.

This is an issue to track this and log any things we have found.

@tomhobson
Copy link
Member Author

it worked like
/lifecycle stale

but did it automatically

@msvticket
Copy link
Member

I don't see any direct support for this in lighthouse. But I see this file:

https://github.com/jenkins-x/lighthouse/blob/master/pkg/config/test_data/config/jobs/kubernetes/test-infra/fejta-bot-periodics.yaml

It seems to be used still in the Kubernetes project:

https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/sig-k8s-infra/trusted/sig-contribex-k8s-triage-robot.yaml

The bot just adds the comment, say /lifecycle stale, and then lighthouse would add label to/close the PR. (Which doesn't require any permissison.)

I'd say that just creating a cronjob that use gcr.io/k8s-staging-test-infra/commenter should work fine. But what was used back in the day for Jenkins X, that I don't know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants