This appears to not be a bug.

Compare the parameter values $JENKINS_URL and $$JENKINS_URL. Jenkins internally resolves placeholders in variables, and dollars are used for that. $$ is an escaped $.

I could offer better documentation though, as this behavior does not seem to be documented in the String Parameter's inline help, but should be.

WDYT?

Relevant Groovy system script (a build step added by Groovy plugin):

def build = Thread.currentThread().executable
def tl = new hudson.util.LogTaskListener(java.util.logging.Logger.getLogger("foo"), java.util.logging.Level.INFO)
println build.getEnvironment(tl).get("STR1")
println build.getEnvironment(tl).get("STR2")

Please tell me what should I do to: get the variable with text from TextBox "as is" (i.e. $$ as $$).

I don't want to resolve variables inside build parameters, I just want to fill file with TextBox contents with something like this in "execute shell":

echo "$TextParameter" > file

And in the $TextParameter sometimes there are "$" and/or "$$" signs which are to be preserved.

same issue for me too. printing out the shell env (env command) shows that the env var is automatically setting

value$

instead of

value$$

Jenkins 2.0, CentOS7

Does anyone know where this behaviour is documented? I cannot find anything about this on https://wiki.jenkins.io/display/JENKINS/Parameterized+Build. Did I miss something?

I wrote down my own experience in https://stackoverflow.com/a/58951240/601203. It's about special handling of whitespace, backslashes and quotes.

I'm seeing the same behavior happening with the AWS Parameter Store Build Wrapper plugin ( https://plugins.jenkins.io/aws-parameter-store/ ). I don't think the issue here is actually in Parameterized Build, I think it's somewhere in Jenkins core...

Good day,

Just to note.
We faced same issue, but we found that declarative pipelines not affected by this interpolation issue.
So we migrated to parametrized declarative pipeline as follows

pipeline {
  agent any
  parameters {
    password(name: 'PASSWORD', defaultValue: 'SECRET', description: 'Enter a password')
  }
  stages {
    stage ("Propogating to environment") {
      environment {
          PASSWORD ="${params.PASSWORD}"
      }
      steps {
          echo "HURA"
          echo "Password: ${params.PASSWORD}"
          echo "Password: ${env.PASSWORD}"
      }
    }
  }
}