Open irvifa opened 4 years ago
/priority important-longterm
/cc @kubernetes/sig-testing I included sig-testing here since we will need advice on how to perform periodic test.
/cc @kubernetes/sig-docs-en-owners
https://github.com/kubernetes/test-infra/tree/master/prow#getting-started
periodic
job type runs periodically.
Thanks @BenTheElder anyway @sftim and @onlydole I’ve checked the periodic jobs on prow https://github.com/kubernetes/test-infra/blob/master/prow/jobs.md however I’m not sure about how often we would like to perform it. Once we agree to the period I’d like to help setup the job.
How about once a week for a proof-of-concept, then the next step would be test every incoming PR (but don't block merges), then we aim to make sure the main branch always passes so we can turn on enforcement for PRs.
?
I think it's (just) fair to label this /sig testing
@sftim Noted then, thank you.
/area web-development
@BenTheElder Do you know if there's a way to clone this repo to the prow job? I notice that the repo and branch is only tightly coupled with presubmit/postsubmit
/retitle Perform Automated Link Checking Periodically
Here's a mockup of how I think the status could show up when link checking fails:
(right now I don't know the magic / code to make that happen though, sorry)
prow cannot do checks currently, due to not being a github app (and the API only being available to apps)
On Tue, Aug 11, 2020 at 11:37 AM Tim Bannister notifications@github.com wrote:
(right now I don't know the magic / code to make that happen though, sorry)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubernetes/website/issues/22489#issuecomment-672177948, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHADK5TLXRUEUT4IPPCE3LSAGFV7ANCNFSM4OYR4F7A .
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-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/remove-lifecycle stale
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
/remove-lifecycle stale
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
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
/remove-lifecyle rotten
@BenTheElder Do you know if there's a way to clone this repo to the prow job? I notice that the repo and branch is only tightly coupled with presubmit/postsubmit
sorry I missed this, yes it's extra_refs
. https://github.com/kubernetes/test-infra/blob/master/prow/pod-utilities.md
lots of jobs clone a repo using this if they're not a pre or post submit
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-contributor-experience at kubernetes/community. /close
@k8s-triage-robot: Closing this issue.
/remove-lifecycle rotten /reopen Noticed someone else had tried removing this label, not sure why it didn't take
@spiffxp: Reopened this issue.
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
/reopen /assign
@shuuji3: You can't reopen an issue/PR unless you authored it or you are a collaborator.
Hello, I'd like to work on this. 🙂
I already wrote a new GitHub Actions workflow file. The remaining task is only to print out the result as annotation: https://github.com/kubernetes/website/issues/22489#issuecomment-672177256
I'm afraid that I'd like to close this issue for now based on the talk on #38866.
/close /unassign
@shuuji3: Closing this issue.
/reopen
It's a valid request even if you don't know how to do this yourself @shuuji3
@sftim: Reopened this issue.
/remove-lifecycle rotten /triage accepted
Another thing is that htmltest doesn't seem to detect cross-page hash. According to my local test results, none of the 19 error of #44573 are detected... Although checking cross-page hash seems to be supported by htmltest , I use the default configuration under website.
This is a Feature Request
In order to provide more up to date link checking, it'll be helpful if we can do automated link checking periodically so whenever we found outdated/dead links we can fixed it immediately.
What would you like to be added
To be able to support this, since we already have this Makefile we can try to run this periodically probably using CronJob or other available infrastructure.
Why is this needed
Comments
It'll help us fixed outdated/dead links we can fixed it immediately.