Validate with libtidy on travis #1990
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
0e39dcf to
fa133e8
Compare
2136bac to
3f421eb
Compare
3f421eb to
b547b1f
Compare
|
We are not using Travis anymore, thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ref #1420
Use libtidy https://github.com/htacg/tidy-html5 to check the build-ed
_sitegenerated on CI.Also update validate-website gem.
Time ~ 10sec for
check:markupcf https://travis-ci.org/ruby/www.ruby-lang.org/builds/504098647#L590Why?
Since #832 we can see that errors happen on markup even it we are using markdown on most of the pages (cf #1418, #1458, #1987 )
The main blocker before was that it increase build time but the complete website check take now ~10sec to ~12sec
cc @stomar @hsbt