Skip to content
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

Migrate CI from Travis CI to CircleCI #44

Merged
merged 7 commits into from
Aug 4, 2018
Merged

Migrate CI from Travis CI to CircleCI #44

merged 7 commits into from
Aug 4, 2018

Conversation

yhatt
Copy link
Member

@yhatt yhatt commented Aug 4, 2018

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:

  • CircleCI's build artifacts can host the outputted coverage HTML per builds.
  • CircleCI's workflow can be composed of several jobs. So in future, we might be able to automate publishing to npm by setting CI jobs.
  • The owner of marp-team is Japanese, so the existence of CircleCI Japan means that we could receive better support about management of marp-team.

@yhatt yhatt merged commit c06a7d7 into master Aug 4, 2018
@yhatt yhatt deleted the circleci branch August 4, 2018 06:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant