On Thursday, July 11, 2024 at 9:18:25 PM UTC+2 [email protected] wrote:
>From reading the Javadoc, I would advise not taking this approach of a custom step. Maybe you want to listen to uses of the stock `build` step and attach some extra information automatically? Or pass a build parameter which would trigger some special behavior? Etc. The goal of the `buildWithEiffel` step is to provide a pipeline step for starting builds with an additional string option that's attached to the Run via an action (so that a QueueListener can pick up the string later on). Passively listening to the stock `build` step won't allow the user to supply the string in the first place. Using a build parameter (possibly of a custom type) to pass the string would technically work, but using parameters as a general key/value store for passing values that aren't meant to reach the actual build seems like a bit of a hack. I'd love for the `build` step to support an extension point whose implementations can receive additional step arguments. Thanks, Magnus (maintainer of the offending eiffel-broadcaster plugin) -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5a2a1cc0-9609-45be-876d-097493bc2ee5n%40googlegroups.com.
