We use Buildkite for CI/CD during software development stages. Our environment includes separate pipelines for different tasks, such as testing, deployment etc... We have 30-40 pipelines in Buildkite
Buildkite
BuildkiteExternal reviews
28 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Buildkite facilitates easy pipeline management and provides hooks and triggers, but has a complex deployment process.
What is our primary use case?
How has it helped my organization?
Initially, we manually configured and ran tests during deployments using Jenkins. After each job, we manually reviewed the reports to identify any test failures and then reported these to the development team. This process created a significant gap between the developers and the testing team.
To address this, we implemented Buildkite. Now, every code change triggers automated tests. We have separate pipelines for each stage of software development, including app testing, system testing, and deployment. This setup functions like a flow diagram: changes in the app automatically progress through the testing and deployment stages. Based on the results, the application is deployed to the server seamlessly.
What is most valuable?
Using Buildkite, managing pipelines becomes much easier. Each pipeline’s output is straightforward to understand, making it simple to edit configurations, Despite an initial steep learning curve, the overall process remains comprehensible. Buildkite also offers features like hooks and triggers; for instance, an action in the app can automatically trigger a pipeline. These elements can be added to specific pipelines, ensuring the entire process is automated.
When changes are made and files are modified in the repository, Automattically with the helo of hooks the Coresponding test pipeline this triggered.The hooks and the use of YAML files are particularly helpful in this process.
What needs improvement?
Since we were using Buildkite for the first time, we initially had a lot of difficulty understanding how it worked. The lack of third-party documentation meant we had to rely solely on Buildkite's documentation, contributing to a steep learning curve. Over time, it became much easier to use, though understanding certain features in Buildkite and YAML Configurations was particularly challenging at first.
Buildkite provides a comprehensive pipeline execution environment. However, in certain instances, Where a pipeline get's failed, pinpointing errors can be difficult. Therefore, when issues occur, understanding the root cause can be trickier and requires deeper analysis.
For how long have I used the solution?
I have been using Buildkite for eight months.
What do I think about the stability of the solution?
We haven't face issues till now.
What do I think about the scalability of the solution?
We haven't had any issue for the scalability part.
Which solution did I use previously and why did I switch?
Previously, we utilized DevOps and Jenkins. With Jenkins, deployment was a manual process; we identified the job and validated it through reports. Now, everything is fully automated with the introduction of Buildkite. For each specific change in the application, the corresponding test pipeline is executed, and deployment occurs only if the pipeline get's passed.
How was the initial setup?
The initial setup is complex. Most work for the pipeline has to be done by the development team. I'm only responsible for the test pipelines from our end.
We began with a POC for the build process, which took around one month. We started by using Azure DevOps, then transitioned from Azure DevOps to Buildkite. It took us some time to configure Buildkite and understand how it works. Eventually, we managed to have it up and running within a week. The entire POC phase lasted around eight to nine months, during which we thoroughly reviewed and refined our plans.
At least ten people were involved in the Buildkite deployment.
What's my experience with pricing, setup cost, and licensing?
We are using the free version of the solution.
Which other solutions did I evaluate?
I was not part of the process
What other advice do I have?
Overall, I rate the solution a seven out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Helps to run jobs and builds docker in layers
What is our primary use case?
Since Docker requires building images to run containers, we use Buildkite.
What is most valuable?
What I like best about Buildkite is its workflow management. You define YAML files to specify what needs to be done. The jobs can run based on a schedule, like a cron job, where you set it to run every night or every week. Additionally, you can set up triggers, such as new pushes to a repository.
It's quite similar to GitHub workflows. The main difference is cost, and Buildkite has some clever features for caching the build process for Docker containers. Docker containers are built-in layers, and code changes don't always mean you need to rebuild all layers. The tool can cache these layers intelligently and only rebuild the parts that need to be updated.
What needs improvement?
The way Buildkite represents workflows can be challenging. It uses Directed Acyclic Graphs, and there's a trade-off between abstraction and understanding what goes wrong when something fails. When a layer of jobs breaks down, it can be difficult to identify the issue at first glance. Additionally, logging can be cumbersome. I prefer GitHub Workflows.
For how long have I used the solution?
I've been using Buildkite for about a year.
What do I think about the stability of the solution?
We never had any issues with stability.
What do I think about the scalability of the solution?
I have not seen any issues with scalability. You can run either one job or a million jobs.
How are customer service and support?
I have never contacted the tool's support team. It has good documentation.
How was the initial setup?
The tool's initial setup and implementation can be difficult. We had multiple teams struggle with it. There are two main reasons for this. First, the abstraction level using YAML can make debugging challenging. Second, DevOps and CI/CD practices are complex for many people.
What's my experience with pricing, setup cost, and licensing?
Buildkite is known to be cheaper than GitHub Workflows, which is considered a standard in the industry. It can be cost-effective, especially for organizations that heavily utilize Docker and containerization, because every code change triggers a new build. Its integration with AWS, particularly with ECR, and its caching capabilities with layers are powerful features.
What other advice do I have?
If you're looking for a product to handle CI/CD workflows, I would rate Buildkite around seven out of ten. I would recommend it to others, depending on their use case. It's a great tool for SRE or DevOps teams, especially in larger organizations with multiple developers and teams continuously producing and changing code.
If you need a platform to separate your repositories and want a more dedicated approach, Buildkite is a choice.
Used for continuous integration, but should offer more options for installing an agent
What is our primary use case?
We used the solution for CI/CD pipeline, continuous integration, and continuous deployment. I used Buildkite for one of the projects in my previous company. I had to use Buildkite for just one project when I worked for a startup.
What is most valuable?
Buildkite is similar to Jenkins. You don't have to set up an agent in Buildkite like in Jenkins. In the Azure DevOps pipeline, you have to install an agent in a separate VM or maybe a Windows agent. Buildkite is like a managed service where the solution manages everything.
What needs improvement?
The solution should offer more options for installing an agent and give users the option of having a separate self-hosted or provisioned agent. The solution's user interface and user access were not that friendly.
What do I think about the stability of the solution?
I did not have any specific issue with the solution’s stability.
How was the initial setup?
The solution's initial setup was challenging compared to other tools, maybe because we were using it for the first time. It was a new tool in the market when we deployed it.
What's my experience with pricing, setup cost, and licensing?
We used the solution’s free version.
What other advice do I have?
Overall, I rate the solution a six out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Used in conjunction with GitHub
What do you like best about the product?
Better integration with Github, Can configure multiple versions and users easily for greater productivity. This solution is very cost-effective compared to other expensive GitHub integration software, and was moreover very well received by the user community as a productivity tool. Our firm is please to recommend this product.
What do you dislike about the product?
It sometimes is unresponsive, and the software just hangs, as though needing memory. Customer service is spotty at best, however we were able to use work-arounds to ease support requirements.
What problems is the product solving and how is that benefiting you?
API building for the STreetOne LLC platform
Recommendations to others considering the product:
Please evaluate your requirements before installing/using
showing 1 - 4