Buildkite is a service which automates your software build and testing processes.
- Scales across hundreds or thousands of agents.
- Run as many as 10,000 agents per account.
- Buildkite uses pipelines that can do more than just builds or tests.
- You can transfer files, build sites or create custom pipeline functionality within your own code to meet your needs.
- Webhooks and APIs enable you to develop custom tools, modify pipelines and configure the agents and pipelines to meet your company's needs.
- The Buildkite agent runs on Windows, OSX and Linux. You can also use the Docker container to run nodes or clusters on any container-enabled platform.
- Integrates with GitHub and other source control tools, to enable you to implement versioning, forking and other standard SCM functionality.
- Buildkite supports many different programming languages, such as Ruby, Haskell, Java and .
- NET. It never accesses your source code, meaning that your custom development and intellectual property are secure.
- The Buildkite agents communicate with the Buildkite API to poll for work. Network connectivity issues may impact your builds or testing.
- While there is a free option for open-source projects, students and teaching organizations, there is a per-user monthly cost to use the software.
- Service-level agreements are not available in the standard plan. They require the Enterprise Plan, which is $2999 per month.
The Buildkite functionality relies on an agent which you install and connect to your source code repository. Once you have done that, you can create a pipeline, define a build and submit it. Just like that! Each agent runs one build at a time, but you can install as many agents as you want. You can then use pipelines to automate your build processes, as well as perform other workflow tasks, such as run scripts, wait for user input, import data or generate a web page. Pipelines can do many handy things, including server provisioning or creating other pipelines. Once your pipelines are running, you can monitor their performance, reliability and status. Over time, you can develop a history of pipeline performance and use that to drive changes to your workflow processes.