-
Notifications
You must be signed in to change notification settings - Fork 1k
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
ci: Weekly check whether the docs url is alive #2482
Conversation
thanks @Bevisy |
b9c55ca
to
5eb44d2
Compare
@Bevisy, sorry for coming late to the party, but why having those checked on weekly basis and not on every PR? |
I can't agree more to add docs check to static-checks ci workflow. Periodic examination results are not sufficiently visual. |
I've changed from periodic checks to triggering checks on every pr push and only triggering checks on all *.md documents when they are modified. make static-check-docs 5.81s user 2.01s system 2% cpu 5:35.94 total If pr does not contain document changes, the execution time as follows: make static-check-docs 0.71s user 0.23s system 10% cpu 9.346 total It can be concluded that the ci time consumption brought is tolerable. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Bevisy!
lgtm
It's worth noting that it might still be worth running this check periodically as well. It's just about possible that we might not get any new PRs for a few days, but if we ran the checks daily, we would detect broken URLs faster. That said, it's more CI time and more complexity so this is fine for now 😄
/test |
Hi, @jodh-intel @fidencio , I found workflow/static-checks always execute docs check if file changed $ /home/zbb/go/src/github.com/kata-containers/tests/.ci/static-checks.sh src/runtime
[static-checks.sh:1148] INFO: Running 'static_check_commits' function
make -C cmd/checkcommits
make[1]: Entering directory '/home/zbb/go/src/github.com/kata-containers/tests/cmd/checkcommits'
go test .
ok github.com/kata-containers/tests/cmd/checkcommits (cached)
go install -ldflags "-X main.appCommit="2b71534dcb403a2341db35ce87a12ff62af793dc" -X main.appVersion=0.0.1" .
make[1]: Leaving directory '/home/zbb/go/src/github.com/kata-containers/tests/cmd/checkcommits'
From github.com:kata-containers/tests
= [up to date] main -> origin/main
Running checkcommits version 0.0.1 (commit 2b71534dcb403a2341db35ce87a12ff62af793dc)
Found 1 commit between commit HEAD and branch main
All commit checks passed.
[static-checks.sh:1148] INFO: Running 'static_check_docs' function
[static-checks.sh:608] INFO: Checking documentation
[static-checks.sh:626] INFO: Checking local branch for changed documents only
[static-checks.sh:663] INFO: Checking document markdown references
... So it means that adding new step/static-doc-check is a duplicate step. Maybe we should add new workflow to check all docs url periodically just as we expected at the beginning I will do some fix later 😄 |
2d054b1
to
f4fb9ed
Compare
I have updated the fix. And when the docks-url-alive-check workflow excuted, we could find there two url dead ERROR: Invalid URL 'https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/filesystems/dax.txt' found in the following files:
docs/design/architecture.md
ERROR: Invalid URL 'https://projectacrn.github.io/latest/tutorials/kbl-nuc-sdc.html#use-the-script-to-set-up-acrn-automatically' found in the following files:
docs/how-to/how-to-use-kata-containers-with-acrn.md The dead url should update to https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/filesystems/dax.rst
https://projectacrn.github.io/2.1/tutorials/kbl-nuc-sdc.html#use-the-script-to-set-up-acrn-automatically |
/test |
/test |
/test-ubuntu-qat |
Any further comments @bergwolf? |
@Bevisy could you please rebase? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Bevisy.
lgtm
@fidencio - could you tal at this one? |
target_branch: ${{ github.base_ref }} | ||
steps: | ||
- name: Install Go | ||
if: ${{ !contains(github.event.pull_request.labels.*.name, 'force-skip-ci') }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that you are using this check at every step. Why not just check this once as the first step and return early if true.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Bevisy ^
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Bevisy Can you address this so that we can have this PR merged?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sorry I don't see the syntax for this feature on github action, it looks like the steps can only be executed one at a time in sequence
Ping for a review y'all! |
Weekly check(at 23:00 every Sunday) whether the docs url is ALIVE, so that we can find the failed url in time Fixes kata-containers#815 Signed-off-by: Binbin Zhang <binbin36520@gmail.com>
/test |
Hold on, we can't simply remove the Travis-related environment variables, but need to do further investigation. I will do some cleaning under issue #3544 and then re-update the validation workflow here. |
A head's up that may affect your PR. In the Architecture Committee meeting from January 25th, 2022, the Architecture Committee has agreed on using the "Dismiss stale pull request approvals when new commits are pushed" configuration from GitHub. It basically means that if your PR has been rebased or updated, the approvals given will be erased. In order to minimize traumas due to the new approach, please, consider adding a note on the changes done before the rebase / force-push, and also pinging the reviewers for a subsequent round of reviews. Thanks for your understanding! Related issue: kata-containers/community#249 |
Adding the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Bevisy!
lgtm
@Bevisy - Could you fix those invalid URL's the checker found on another commit on this PR maybe? |
Weighing up the duplication versus the ability to check all our docs daily, I say let's land this! inter-step comms and skips are extremely awkward with GHA's, so if that language every grows the ability to do what we want in a simpler way, we can iterate this GHA later imho. |
Ping for more reviews folks... |
Can we get one more review here please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. OOI where would we see an unsuccessful run? It wouldn't be in the PRs, right?
We can see the results of the execution in the actions. We don't get email notifications, so we need to check the results of the actions periodically. |
/test-ppc64le |
/test-ppc |
/test-power |
To give a bit of context to this PR:
|
Weekly check(at 23:00 every Sunday) whether the docs url is ALIVE, so that
we can find the failed url in time
Fixes #815
Signed-off-by: Binbin Zhang binbin36520@gmail.com