-
Notifications
You must be signed in to change notification settings - Fork 181
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
Improving link management under CI/CD #737
Comments
For the Ubuntu link, my browser is redirected here: http://old-releases.ubuntu.com/releases/18.04.4/. I will see if changing to this addresses the problem. The Schematron link returns a page reporting a database connection error. (It is interesting that this is detected as a failed link.) One possible alternative would be the Github repo of the (de facto) reference implementation: https://github.com/Schematron/ I will push up changes next and make a PR; if it passes the link checker we can look at the edits. Next: rebasing other branches (at least those behind pending PRs); any policy considerations going forward. |
We fixed the broken links, but we still need to address a more permanent mechanism for managing broken links. The approach going forward needs to allow for minimal disruption to the typical developer working in the repo. |
Will fix this in #1208 now that Metaschema equivalent of tooling improvement was merged, fixed, and approved by Dave. |
User Story:
The CI/CD process includes a script to perform link checking. This is very useful, ensuring that the OSCAL web site does not present users with broken links.
But this becomes an impediment when a link breaks. When a linked page or site is no longer available, our builds fail until the offending link is removed or replaced. However, a developer making a PR frequently does not have knowledge or authority for changing a link in a page having nothing to do with the actual work in the branch.
Currently (at time of writing) this is happening with two links, both in the file
build/README.md
:Goals:
Dependencies:
None known.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: