Hello,
Could you post a minimal Jenkinsfile that reproduces the issue, and also
clarify which screen you're initiating the run from? It could possibly be a
bug that needs fixing. It would greatly accelerate our reproducing the
issue if you can provide what I requested above.
Thanks,
Cliff
On Tue
I have a Jenkinsfile, which includes this:
parameters {
string(name: 'Stack', defaultValue: 'DEV', description: 'For which
environment is this?')
string(name: 'Version', defaultValue: '3.2.0-beta.0', description: 'What is
the release version?')
}
And works great, running it in the "regu
