Closed jufemaiz closed 6 years ago
Thanks for submitting this @jufemaiz! Those use cases sound like stuff we've bumped into ourselves before. Is one of those cases the problem you're trying to solve at the moment?
@keithpitt we've just hit one area where I would like to ensure that there is an authorised list of users able to unblock (in our case it's infrastructure via terraform builds, but we will have another in the coming months which is around delivery of a complete platform for partners, which needs a commercial sign off so we don't want to have unauthorised users hitting go).
We'd also like to be able to use the details of the user who unblocked it to notify them directly, notify the head of product/infrastructure and notify myself that person X has unblocked a step.
@jufemaiz cool cool - thanks for explaining for me!
Is the work around working OK for the moment? (Even thought it's a little yucky)
@keithpitt haven't quite implemented it yet, still designing it :)
No worries :) Lemme know how it goes!
This sounds pretty neat, we're starting to look at using Buildkite with Terraform and would definitely value this functionality.
We've just added the environment variables BUILDKITE_UNBLOCKER
, BUILDKITE_UNBLOCKER_UUID
and BUILDKITE_UNBLOCKER_TEAMS
to build jobs after a block step 🎉
https://buildkite.com/docs/pipelines/environment-variables
I see it in the documentation, and I tried to use this, but it's not showing up? I unblock a step, but the environment variable doesn't show up in the job that comes after the block.
@SEAPUNK that’s odd, it should be there - do you want to shoot Support an email with a link to the build you’re seeing this happen in?
Yeah, I contacted support, and they fixed it. Thanks!
Ref: https://github.com/buildkite/feedback/issues/213#issuecomment-275977898
Use cases include:
Obviously there's some issues with permissions (e.g. fail it, but the details are then in the branch if using pipeline.yml and hence they'll allow it on retry, though hopefully from a process perspective the failed build should raise eyebrows).
Current workaround recommended by @keithpitt: