We're seeing this same behavior today running Pipeline: Job (workflow-job) 2.32 (on Jenkins 2.176.1 LTS), with the "Lightweight checkout" checkbox unchecked. Is there a possibility that the system is still choosing a lightweight checkout essentially "on the fly", and if so, is there a way to force a heavyweight checkout?

Aha – for us the issue was that we were reading a file from the workspace before the start of the the pipeline block, using a command like `def common = evaluate readTrusted('./Common.groovy')`. This seems to have bypassed the variable resolution. Removing this line caused the expected behavior to start again.

We have still a problem with Pipeline: Job 2.32 (even after upgrade to 2.36) on Jenkins 2.179. "Lightweight checkout" checkbox unchecked. Parameter Expansion does not work if parameter comes from "Properties File Path", It works, however, with parameter from "Properties Content". Too bad.

BTW, our properties file is correct because it previously worked with a freestyle job.

I created new issue JENKINS-60250.

I could confirm that using `readTrusted` causes such error.

We have same problem, but in our case we don't have readTrusted
But we are using kubernetes with kubernetes-plugin, and we were using yaml file for pod configuration

  agent {
    kubernetes {
      yamlFile "pod.yaml"
    }
  }  

seems that underhood it calls readTrusted
we tried to use

  agent {
    kubernetes {
      yaml readFile("./pod.yaml")
    }
  }

but this also didn't work
only inline pod yaml helped to solve this issue

agent {
    kubernetes {
      yaml """
apiVersion: v1
kind: Pod
spec:
  containers:
  - name: jnlp
    image: imagename
    imagePullPolicy: Always

"""
    }
  }