If Jenkins job "A" has a configured fstrigger-trigger, then some other Jenkins jobs "B" (not all) will inherit the job "A" value for their ${WORKSPACE} env-variable. Keeping job "A", but removing the fstrigger and restarting Jenkins, will solve the issue. Adding an explicit WORKSPACE to all "B"-jobs will solve the issue. Job "A" does not directly use the envinject plugin, but "B" jobs do.