Buildkite

I use Buildkite for deployment tasks related to building AMI images and deploying routing profile queues into Amazon Connect. This involves using Buildkite in conjunction with GitHub. We create files, raise pull requests in GitHub, and then run the Buildkite pipeline for deployment tasks.

In Buildkite, I find it easy to manage the Buildkite pipeline with the ability to pull Buildkite IP directly to update security groups. The default upgrade is managed by Buildkite. We use version five integrated with Terraform. There is a team that assists with any significant issues, which adds to the reliability.

One area that needs improvement in Buildkite is the requirement for rework of the code. There can be syntax errors when running the Buildkite pipeline, especially if someone has made manual changes in AWS or Amazon Connect, which can cause the pipeline to stop.

I have been using Buildkite for two years.

We have faced multiple instances of syntax errors when running the Buildkite pipeline, especially when manual modifications have been made into AWS or Amazon Connect. While these issues occur, we rely on a dedicated team to manage and resolve significant issues.

The team managing Buildkite provides good support, and they handle significant issues that arise during operations.

Neutral

The initial setup is not something I witnessed directly as the pipeline was already in place when I joined. Therefore, I have no firsthand information about the initial setup process.

We are migrating our Buildkite pipeline to another tool, but I am not aware of why this decision was made. This migration capability is considered a pro.

With two years of experience on Buildkite, I would recommend it to others due to its manageable pipeline and the support team available for big issues. I am satisfied with it, rating its stability an eight out of ten. Overall, I rate Buildkite eight out of ten.

The tool is simple and has no learning curve. If you know YAML, you can master it. It is simple to learn. 

As a newbie, I think BuildKite has several issues. For example, it can't get the status of a PR once it's closed. The syntax is easy to use, but updating a pipeline requires administrator settings, and viewing pipelines for others isn't straightforward.

Another issue is the lack of additional support, especially with plugins. Most plugins, except for a few like Docker, aren't updated regularly on GitHub. While we haven't faced major issues, having someone actively maintain these plugins would increase confidence.

I have been working with the product for two years. 

The tool's support comes up with a solution, but its limitations affect it. 

Positive

The tool's deployment is straightforward. 

I rate the overall product an eight out of ten. 

Most of our projects involve both front-end and back-end development. We write the code and then create a file to set up our process, including specifying the tests we want to run. Before deploying to production, we need to install and configure certain things. We need something like Docker Pro, but I'm unsure about that. I'm familiar with the steps for using Buildkite for this process. We start by defining which tests to run.

Once the tests are done, we can add a button to ensure the process doesn't proceed until the test is completed or until we manually press the button. We do this because we always have multiple stages of development, like dev, staging, and production. Once the code is deployed, we test it on dev and then press the button to move it to the stage for QA testing. After QA, we press the button again to deploy to production.

If you join our team, it's very easy to learn Buildkite. We have our own boilerplate, so you can just clone it and add your configuration steps. Plus, we have documentation available to guide you through the process.

I have been using the product for two years. 

Sometimes, the system breaks down when we have limited instances running. For example, our company is very large, and some share the Buildkite instances. If we expect to deploy to production on a Friday, but every team is also deploying on Friday, we might have around twenty projects using Buildkite simultaneously.

My company has 1000-2000 users. The solution is scalable. However, we are careful so as not to overspend. 

The solution is worth its cost if you are a large organization. It is flexible and easy to use. 

I haven't used any other CI/CD platform before this, except for GitLab CI/CD, which I only used at a surface level. We would write some build steps and deploy them as soon as the tests were done. I'm unsure if GitLab has the same capabilities as Buildkite, particularly the step configuration feature that allows you to customize and control the move from one stage to the next (dev to staging, staging to production). I find this feature in Buildkite very easy to integrate and use.

If you're considering using the solution for the first time, I suggest starting with GitLab CI/CD or GitHub Actions. Buildkite might be overkill for smaller projects or individual use. It's usually more expensive for new users but can be cost-effective for large-scale organizations. 

I rate the overall product a nine out of ten.