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

"""
    }
  }    

The issue still persists. I identified 3 modules that need to be fixed. The 

scm-api plugin does not forward the Run<?,?> to SCMFileSystem builder

git plugin would need to implement a new builder that would use the Run<?,?>

workflow-cps plugin needs to send the Run<?,?> to the scm-api in the CpsScmFlowDefinition.java to SCMFileSystem.of (which needs to be extended)

I have implemented a fix on my local machine, I have a draft opened on github although I would need some feedback, if this seems OK for the devs https://github.com/jenkinsci/scm-api-plugin/pull/160 if I am on right track
Also I got on my PC fix on the other 2 repos so It was working, although this will require some magic to make it production quality

I wondered whether I should file a request to make BitbucketSCMFileSystem in the Bitbucket Server Integration plugin implement the method that was added to SCM API. However, it seems this bug is not currently reproducible with Bitbucket Server Integration because it does not yet support lightweight checkout for this scenario. Therefore, I'm not filing such a request.

I tried to reproduce this issue with Jenkins 2.346.2, Bitbucket Server Integration plugin 3.2.2, Git plugin 4.11.4, SCM API plugin 620.v0a_5b_1f8054c0, and Pipeline: Groovy plugin 2759.v87459c4eea_ca_. Jenkins logged "Lightweight checkout support not available, falling back to full checkout", created a Git repository on the Jenkins controller, fetched refs/heads/* from the remote, resolved the commit ID of ${PIPELINE_BRANCH}, checked out that commit, and read the pipeline from the worktree. If I understand correctly, a lightweight checkout using the Bitbucket Server Integration plugin would have requested the file content from the Bitbucket Server REST API instead of creating a Git repository on the Jenkins controller, and a lightweight checkout using the Git plugin would have streamed the blob from the Git repository instead of checking out all the files.