Invalid condition "always" - valid conditions are [always,

My team’s Jenkins server just started getting the following error message with our multibranch pipeline. Earlier today there were some plugins that got updated —listed below as well. Any idea why these conditions, which are clearly supported, are not being recognized? Which plugin might be causing this issue? And should we just revert it or what is the best option?

Jenkins 2.263.3

Plugins recently upgraded:

pipeline-stage-tags-metadata 1.9.0
pipeline-model-api 1.9.0
pipeline-model-extensions 1.9.0
pipeline-model-definition 1.9.0
cloudbees-folder 6.16
cloudbees-bitbucket-branch-source 2.9.10
git-client 3.9.0
git 4.8.1

Error message

These conditions are inside a post { } block

Invalid condition "always" - valid conditions are [always, changed, fixed, regression, aborted, success, unsuccessful, unstable, failure, notBuilt, cleanup]

 Invalid condition "unsuccessful" - valid conditions are [always, changed, fixed, regression, aborted, success, unsuccessful, unstable, failure, notBuilt, cleanup]

Invalid condition "success" - valid conditions are [always, changed, fixed, regression, aborted, success, unsuccessful, unstable, failure, notBuilt, cleanup]
1 Like

It’s https://issues.jenkins.io/browse/JENKINS-66247 there’s a PR up to fix it, I assume it will get released today

1 Like

Thank you timja. I’ll keep my eye on this.

The plugin has been released now

2 Likes