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

Use only one CI tool rather than two #4022

Closed
sichvoge opened this Issue Mar 28, 2018 · 5 comments

Comments

Projects
None yet
3 participants
@sichvoge
Copy link

sichvoge commented Mar 28, 2018

Currently, the Prometheus project is using two different CI tools (CircleCI and Travis). I understand that there were reasons to do that such as Travis is much faster running tests but it did not support Docker in the past. Hence, CircleCI was introduced.

But as Travis added support for Docker, shouldn't we only one? I know that there is probably no harm on running two, but managing a single CI process is probably easier. If that makes sense, I'd be happy to help migrating.

cc/ @brancz

@krasi-georgiev

This comment has been minimized.

Copy link
Member

krasi-georgiev commented Mar 28, 2018

I have a proposal coming in 1-2 days for https://github.com/drone/drone
As part of the new prombench and e2e CI tests can also combine all steps in circle and travis so will post a link here if you want to join the discussion.

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Mar 28, 2018

Keep in mind that we also use CircleCI as part of our Go releases.

@krasi-georgiev

This comment has been minimized.

Copy link
Member

krasi-georgiev commented Mar 28, 2018

yes, I am aware, thanks.
I have looked through all build steps.

@krasi-georgiev

This comment has been minimized.

Copy link
Member

krasi-georgiev commented Mar 28, 2018

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 22, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 22, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.