Lachlan Donald

I'd argue this is the sensible default and that folks with weird workflows should opt-out of it.

Version detection with git sounds like a good thing to have @keithduncan.

> So I think this could cause performance issues for that sort of thing. @jradtilbrook given the commit object is already being pulled down, is there reason to think adding...

@jradtilbrook yeah honestly I’m not sure either!

Without this behaviour in place, I've experienced users frequently running into weird race conditions where the latest reachable tags are based on which build on the host has fetched tags...

If sent a `SIGTERM` the agent will stop accepting new work but finish it's current job. I'd be tempted to solve this with a cronjob that checked health of the...

Yeah, `post-exit` is one I've wanted for quite a while. The other option that we've been pondering is a `pre-accept` hook that runs before the agent accepts and provides an...

Looking at the trace, I see `SIGQUIT: quit` at the top. It's possible that this was actually the `buildkite-agent` terminating the bootstrap with an unhandled `SIGQUIT`. Are you seeing this...

This is looking awesome!

@toolmantim could we check for the agent version on the server side and trim off the digest for agents that don't support it? We do pre-processing of the plugins currently....