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

Fix help.github.com link checks #3155

Merged
merged 2 commits into from
Apr 29, 2022

Conversation

cfergeau
Copy link
Contributor

For some reason, help.github.com will only serve compressed content, and
will reply with a 403 error without any "Accept-encoding" headers.
This causes 'make docs_check_links' to report help.github.com links as being
dead.
This issue is tracked in github/docs#17358

For this fix to work, quay.io/crcont/docs-builder:latest must be rebuilt
and pushed to quay.
This can be rebuilt and tested locally with:

$ (cd images/docs-builder && podman build -t quay.io/crcont/docs-builder:latest .)
$ make docs_check_links

In the next commit, we will add additional config entries unrelated to
the ignorelist we currently have.
@openshift-ci openshift-ci bot requested review from jsliacan and praveenkumar April 29, 2022 09:20
@cfergeau cfergeau changed the base branch from master to main April 29, 2022 09:39
@praveenkumar
Copy link
Member

Why no github action run on this PR?

For some reason, help.github.com will only serve compressed content, and
will reply with a 403 error without any "Accept-encoding" headers.
This causes 'make docs_check_links' to report help.github.com links as being
dead.
This is tracked in github/docs#17358

For this fix to work, quay.io/crcont/docs-builder:latest must be rebuilt
and pushed to quay.
This can be rebuilt and tested locally with:

$ (cd images/docs-builder && podman build -t quay.io/crcont/docs-builder:latest .)
$ make docs_check_links
@cfergeau cfergeau force-pushed the asciidoc-link-check branch from 5b415a1 to 1ac7b33 Compare April 29, 2022 09:59
@openshift-ci
Copy link

openshift-ci bot commented Apr 29, 2022

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please ask for approval from cfergeau after the PR has been reviewed.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@cfergeau
Copy link
Contributor Author

Why no github action run on this PR?

Maybe because it was initially based on origin/master which has no github actions instead of origin/main

@cfergeau
Copy link
Contributor Author

(NB: the "build and publish docs" failure is expected as the quay.io docs-build image hasn't been updated yet with the changes from this PR)

@openshift-ci
Copy link

openshift-ci bot commented Apr 29, 2022

@cfergeau: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-crc 5b415a1 link true /test e2e-crc
ci/prow/integration-crc 1ac7b33 link true /test integration-crc

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@cfergeau
Copy link
Contributor Author

(NB: the "build and publish docs" failure is expected as the quay.io docs-build image hasn't been updated yet with the changes from this PR)

I've pushed the quay.io/crcont/docs-build image with the changes from this PR to quay.io, this should fix docs link checks for this PR and also for the other PRs.

@praveenkumar praveenkumar merged commit 5565077 into crc-org:main Apr 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants