SecretText vs File Credentials: Binding to Environment Variables or Temporary Files in Jenkins Pipelines?

The goal is to run integration tests that require a secret token without pulling in production credentials. The Jenkins Credentials Binding plugin offers withCredentials blocks that can bind SecretText and File types to environment variables or temporary files.

In scripted pipelines, I need the secret token as a file for a downstream script, but the plugin only writes File credentials to disk. Binding a SecretText to a file is not documented and appears to fail with an “unsupported binding” error.

Additionally, the API does not allow multiple credentials of the same type in a single withCredentials call, which would simplify passing several tokens to different tools.

Is there a supported way to bind a SecretText credential to a temporary file in a scripted pipeline, or must I create a File credential instead? Can I bind multiple SecretText credentials simultaneously, or is the current API limited to one per type?