It would be useful if details of:
- Cron target (name)
- Requestor (i.e. user that issued
dron build promotecommand)
were included in:
- Starlark Context
- Drone Environment Variables
For example, there’s already a
ctx.build.sender parameter, but this appears to always be the same as the
author (but the promotion request could well have been requested by someone other than the commit author).
Adding the Cron target/name (as an env var) would allow for pipeline steps to include target-specific logic - at the minute, I’m having to define multiple steps, each with a different
when clause and everything else the same except for a single parameter within the commands.