Due to a change implemented in JENKINS-21013(FileBuildParameters.java: ~100), if the workspace does not exist, the attempt to read parameters from that file is skipped. However, there is nothing that restricts the parameter file to be in the workspace, so the check is inaccurately flagging that the parameter file doesn't need to be searched for.

I place parameter files in ${WORKSPACE}/.. so that I could use the workspace cleanup plugin along with the trigger parameterized build plugin. Since the workspace is cleaned up on jobs first, now the parameterized build trigger skips the check and doesn't read the parameter file, even though it exists. I would think this is a fairly typical use case scenario, but have no evidence to support this.

It would be nice if that check was taken out, so parameter files could once again be anywhere on the build slave.