|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I get the same warnings and the build pipeline does not work, but not because of the build pipeline plugin.
I have 1.500 Jenkins version and the latest build pipeline plugin. In the past, it worked ok. But after I updated the Env-inject plugin from 1.72 to 1.81, this stacktrace warning and build pipeline failure appeared.
In my opinion, this bug is caused by env-inject plugin (I don't know exactly what version between 1.72 and 1.81 introduced it) because the build pipeline was released with this version long before the env-inject increased its version.
Downgrading the build pipeline plugin only hides the issue and not solves it. I tried this, but the pipeline view was some kind messed up (it didn't displayed the pipeline parameters).