Block steps have a great syntax for creating forms. But the “Create Build” UI only has a big text box for environment variables.
It would be great if there was a way to customize the “Create Build” form with the same features as Block steps have.
for this!
Some of the most common feedback I hear from folks using my team’s pipelines is “where do I fill in this field?” thinking something is missing since it isn’t in the “Create Build” form, or they don’t catch the button to click the block step.
For “Buildkite veterans” the block/input steps make sense, but for users not super familiar it can feel unintuitive.
It would be great if there was maybe a separate place in a pipeline’s settings to drop a piece of YAML for an initial set of input fields that would get merged into the “Create Build” form if it makes sense?
Thanks @evandam @jamiebuilds!
This is a great suggestion, I have taken this and shared it back with the team!
+100 - A few small UI changes here would make the product a lot easier for many end users to understand.
Things id love to see:
- Ability to customize button text per pipeline (New Build → New Deploy or etc.)
- Ability to hide all inputs
- Ability to define custom default build message (ex. extract a human readable version or etc)
yes! definitely a much needed feature.
+1!! We use a lot of environment variables as feature flags to enable/disable certain functionality in our dynamic pipeline. Only those developers that know about said environment variables are able to use them so exposing it in the UI would increase adoption and make it a lot easier to use
Hi @jaimeb I can see how better visibility into feature flags would make the pipeline more intuitive and easier to use. I’ll be sure to take this feedback to the team and share your insights!