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

Adding a jenkins job config for linkchecker #21193

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
33 changes: 33 additions & 0 deletions hack/jenkins/job-configs/test-linkchecker.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
- job:
name: 'kubernetes-test-linkchecker'
description: |
Grab the latest from GitHub, then run hack/verify-linkcheck.sh.<br>
Test Owner: Build Cop
logrotate:
numToKeep: 200
builders:
- shell: './hack/verify-linkcheck.sh'
publishers:
- claim-build
- gcs-uploader
- email-ext:
recipients: 'xuchao@google.com'
scm:
- git:
url: https://github.com/kubernetes/kubernetes
branches:
- 'master'
browser: githubweb
browser-url: https://github.com/kubernetes/kubernetes
wipe-workspace: false
skip-tag: true
triggers:
- timed: '@daily'
wrappers:
- ansicolor:
colormap: xterm
- timeout:
timeout: 60
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this really take an hour to run?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It takes more than 20 minutes on my local machine. And the time varies depending on how many 503 the tool gets, so I choose 60 minutes.

fail: true
- timestamps
- workspace-cleanup