ci(v2): fail CI if build takes too much time #4516
Merged
Conversation
This file contains 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
…-v4/persistent-cache-v5 + webpack terser cache
slorber
added
the
pr: maintenance
|
[V1] Deploy preview success Built with commit e9e86e4 |
|
Deploy preview for docusaurus-2 ready! Built with commit e9e86e4 |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-4516--docusaurus-2.netlify.app/ |
|
Size Change: 0 B Total Size: 576 kB ℹ️ View Unchanged
|
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.
Motivation
CI should fail if the build takes more time than the timeout.
This will mostly be useful to compare between master/webpack4 VS webpack5 incremental build perfs (#4089)
docusaurus clearshould also clear the full.cachefolder (ie Terser cache too) so that the comparison is more relevant