Run CircleCI builds every day #573
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
ilammy
force-pushed
the
circleci-cron
branch
from
62c58c7
to
eae143b
Compare
Modern ecosystem needs to go fast, die young, break early, and ship often. Therefore we can never be sure that if a commit was successfully built today then the same code can be built tomorrow. Transitive dependencies come and go, new toolchain versions get released, etc. We do not have every dependency pinned, so we should be testing regularly to see if anything breaks. Let's run CircleCI test suite every day at 5:00 to make sure that we see the scheduled breakage early in the morning, not when some poor soul submits a pull request and *then* learns that something does not work.
ilammy
force-pushed
the
circleci-cron
branch
from
eae143b
to
1a100a1
Compare
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.
Modern ecosystem needs to go fast, die young, break early, and ship often. Therefore we can never be sure that if a commit was successfully built today then the same code can be built tomorrow. Transitive dependencies come and go, new toolchain versions get released, etc. We do not have every dependency pinned, so we should be testing regularly to see if anything breaks.
Let's run CircleCI test suite every day at 5:00 to make sure that we see the scheduled breakage early in the morning, not when some poor soul submits a pull request and then learns that something does not work.
Checklist