I found lambCI which seems best but too bad it doesn't support bitbucket. Which tool do you use?
Travis costs several hundred dollars for 3-4 consecutive build
Ask HN: What CI tool do you use in 2019?
1–8 of 8 posts
Re: Ask HN: What CI tool do you use in 2019?
#2I have used Codeship Standard, CircleCI 1/2, and Semaphoreci 1. If you want a lot of flexibility I would suggest going with Circle. If you want a super cost effective option maybe look into Semaphoreci but it's more limited and less polished.
Re: Ask HN: What CI tool do you use in 2019?
#3Distelli (now puppet pipelines) let's you run as many builds as you want on your own hardware.
Re: Ask HN: What CI tool do you use in 2019?
#4Jenkins
Re: Ask HN: What CI tool do you use in 2019?
#5I have used Codeship Standard, CircleCI 1/2, and Semaphoreci 1. If you want a lot of flexibility I would suggest going with Circle. If you want a super cost effective option maybe look into Semaphoreci but it's more limited and less polished.
Out of curiosity (CodeShip founder here), what could we have done better?
Re: Ask HN: What CI tool do you use in 2019?
#6Jenkins
Jenkinsfiles. Helps a lot when growing to more environments, toolset versioning in the code and environment reproducibility via Docker containers.
Also best practice is to fork the Dockerfiles and build and host your own images in a registry.
Re: Ask HN: What CI tool do you use in 2019?
#7Semaphore (https://semaphoreci.com) recently introduced pay-per-use model with autoscaling, so you don’t have to pay a large sum just to run a few parallel jobs (disclaimer: cofounder here, open for questions).
Re: Ask HN: What CI tool do you use in 2019?
#8I have used Codeship Standard, CircleCI 1/2, and Semaphoreci 1. If you want a lot of flexibility I would suggest going with Circle. If you want a super cost effective option maybe look into Semaphoreci but it's more limited and less polished.
Thanks for using Semaphore Mike. Have you tried the new 2.0?