We've just released a new Buildkite Agent stable version: 2.1.5 🎉

This release fixes a few minor issues we've seen since the previous stable version, including:

• Amazon Linux upstart was killing agents too aggressively, causing spurious build failures when auto-scaling (#244)
• Timeouts were always sending a SIGTERM instead of any configured signal (#215)
• Fetching specific git commits doesn't fetch refs and was causing checkout failures, and some other minor git fetch issues (#243)

This last issue has been cropping up for several users. It usually looks something like:

$ git fetch -q origin abc123 2> /dev/null || git fetch -q
$ git reset --hard origin/my-branch
fatal: ambiguous argument 'origin/my-branch': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

This release has been published to the Buildkite package repositories. For instructions on upgrading your agent please see the Upgrading section in the corresponding section of our installation documentation.

For a full list of what's changed and downloadable binaries head on over to the GitHub release page.

Happy building! 😁

If you’ve ever needed to re-run a job locally using the same environment variables that were used in a build, we’ve some good news: the Environment tab on each job now shows the values in a shell-friendly format for easy copy and pasting. 📄🐢

BUILDKITE_BUILD_NUMBER="956"
BUILDKITE_COMMAND="echo \"Oh hai\""

We've also added a “Show export Prefix” button which prefixes each line with bash’s export builtin command, for easily re-running scripts or processes with those values:

$ export BUILDKITE_BUILD_NUMBER="956"
$ export BUILDKITE_COMMAND="echo \"Oh hai\""
$ ./my-script.sh

Happy script debugging! 🕷️

We've just shipped upgrades to one of the most important systems within Buildkite's infrastructure 😏

All of the emojis from the latest unicode specification can be used in Buildkite, such as 🦄, 🐿️, and skin tone modifiers:

👍🏿 \:+1\:\:skin-tone-6\:
👍🏾 \:+1\:\:skin-tone-5\:
👍🏽 \:+1\:\:skin-tone-4\:
👍🏼 \:+1\:\:skin-tone-3\:
👍🏻 \:+1\:\:skin-tone-2\:
👍 \:+1\:

See all the emojis we support (including custom ones like ) over on our GitHub Emojis repository

Our JavaScript Emoji Technology™ is now open source on GitHub including a Webpack loader and a ES6 string parser. Feel free to have a look to see how it all works 🕵

And don't forget… with great power, comes great 🌯

Welcome to the first Changelog update! ✨ This is where we’ll keep you up-to-date with the small improvements we’re constantly rolling out. The big stuff will still make it onto the blog, but if you’re a daily Buildkite user there’s lots of other changes you’ll want to know about.

Now, onto the first update… 😄

You may have noticed that we’ve recently renamed Projects to Pipelines, both in the web interface as well as the API. We’ve been wanting to make this change for a while because there's nothing project-y about Buildkite—we’re not a project management tool, our job is to help you build amazing software delivery pipelines 🔨📦🚀

To coincide with the rename we’ve made a Sample Pipelines GitHub repository to help discover and share the different ways of using pipelines, such as how to dynamically generate pipelines and trigger dependent pipelines. There’s also now a handful of examples for common languages and tools. Please send through a pull request to update the Readme if you have your own example you’d like to share ❤️

You can also use the new \:pipeline\: emoji, perfect for your pipeline upload steps. It looks like this:

The REST API has been bumped to v2, and the webhooks to v3, to incorporate the rename. For the API see our notes for what's changed from v1 to v2, and to upgrade your webhooks simply browse to the webhook and hit the Upgrade button 👍