Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upUse only one CI tool rather than two #4022
Comments
This comment has been minimized.
This comment has been minimized.
|
I have a proposal coming in 1-2 days for https://github.com/drone/drone |
This comment has been minimized.
This comment has been minimized.
|
Keep in mind that we also use CircleCI as part of our Go releases. |
This comment has been minimized.
This comment has been minimized.
|
yes, I am aware, thanks. |
This comment has been minimized.
This comment has been minimized.
|
lets continue the discussion in |
krasi-georgiev
closed this
Mar 28, 2018
This comment has been minimized.
This comment has been minimized.
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
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.
sichvoge commentedMar 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