Migrate CI from Travis CI to CircleCI #44
Merged
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.
Migrate CI from Travis CI to CircleCI. This PR is a feedback from
@marp-team/marp-core
.We feel that Travis CI build performance is not fast so much. Sometimes there was a time lag. The lagged build triggers with about a minute lag after pushing.
So we have tried using CircleCI on
@marp-team/marp-core
. The code base does not much bigger, but we satisfied with the great build performance on CircleCI, that only spends about a minute without lags for building!One of the cons is that the configuration becomes complicated, but we receive many pros instead: