There are now three different before attributes for when which are evaluated in this very order:
beforeOptions
beforeInput
beforeAgent
The documentation tries to describe this "highlander principle" but it would be much more logical and readable if there was only a single attribute before allowing only a single value of options, input or agent. E.g.:
There are now _three_ different {{before}} attributes for {{when}} which are evaluated in this very order: - {{beforeOptions}} - {{beforeInput}} - {{beforeAgent}}
The documentation tries to describe this "highlander principle" but it would be much more logical and readable if there was only a single attribute {{before}} allowing only a single value of {{options}}, {{input}} or {{agent}}. E.g.: {noformat}
when { before 'options' // ... }
{noformat} Migration consideration: The old dedicated {{before}} attributes should not be removed right away. Instead those attributes should be marked deprecated and their usage should yield warnings in the log.
There are now _three_ different {{before}} attributes for {{when}} which are evaluated in this very order: - {{beforeOptions}} - {{beforeInput}} - {{beforeAgent}}
The documentation tries to describe this "highlander principle" but it would be much more logical and readable if there was only a single attribute {{before}} allowing only a single value of {{options}}, {{input}} or {{agent}}. E.g.: {noformat} when { before 'options'
git
// ... } {noformat} Migration consideration: The old dedicated {{before}} attributes should not be removed right away. Instead those attributes should be marked deprecated and their usage should yield warnings in the log.
Liam Newman While I am always glad to help improving Jenkins (plugins) I currently don't have time for this, sorry.
PS: Are you sure about changing the example from before 'options' to before git? Right now we don't have beforeGit, so do you have something new in mind?