Skip to content
This repository has been archived by the owner on Jan 10, 2024. It is now read-only.

Consider switching from Travis-CI to Circle-CI #226

Open
ericwb opened this issue May 8, 2019 · 2 comments
Open

Consider switching from Travis-CI to Circle-CI #226

ericwb opened this issue May 8, 2019 · 2 comments
Labels
discussion An issue/pull request for discussion enhancement New feature or request task-size-large

Comments

@ericwb
Copy link
Collaborator

ericwb commented May 8, 2019

Is your feature request related to a problem? Please describe.
Circle-CI is much faster and good for container-like deployments such as Precaution. Travis-CI is more appropriate for tools that need cross-platform testing.

Describe the solution you'd like
Switch the build tool app to Circle-CI.

Describe alternatives you've considered
Continue with travis-ci.

Additional context
https://circleci.com/integrations/github/

@ericwb ericwb added the enhancement New feature or request label May 8, 2019
@ericwb
Copy link
Collaborator Author

ericwb commented May 28, 2019

ansible/molecule#1770

@MVrachev MVrachev added discussion An issue/pull request for discussion task-size-large labels Sep 2, 2019
@ericwb
Copy link
Collaborator Author

ericwb commented Sep 6, 2019

I believe now that GitHub actions are a better way to go. Of course, we'd have to wait till Actions are generally available. Here's an example:
https://github.com/ericwb/bandit/pull/3

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
discussion An issue/pull request for discussion enhancement New feature or request task-size-large
Projects
None yet
Development

No branches or pull requests

2 participants