In case anyone else runs into this; the problem was nothing to do with
Jenkins, it was a change I'd made to the second script, which hid all
output internally. Coincidence that both changes went in together!
On Monday, 4 February 2019 12:16:53 UTC, James Telfer wrote:
>
> Hi,
>
> I'm pulling so
Hi,
I'm pulling some common functionality out of my pipelines into a global
library. I've come across the following odd (and unwanted) behaviour;
The original, Declarative Pipeline did something like this:
pipeline {
...
stages {
stage('Build') {
steps{
bat 'call setup-en
