Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-40112

Having '=' in injected variable value, erases build history after running JobDSL

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Minor Minor
    • None
    • Jenkins ver. 1.609.3;Environment Injector Plugin 1.93.1;JobDSL 1.45

      Looks like EnvInject and/or JobDSL have a bug.

      Steps to reproduce:

      1. Set up a job that runs this JobDSL:

      `job('run_deploy_mock') {
      steps {
      environmentVariables

      { env('deployedArtifacts', 'component1=1.0.0.2') }


      }
      }`

      2. Run it and it will create a job called 'deploy_mock'
      3. Run the 'deploy_mock' job. After build #1 is done, go to build details and check 'Environmental Variables' section for an entry called 'component1'
      4. Run the JobDSL job again
      5. Check 'Environmental Variables' section for 'deploy_mock' build #1. The 'component1' variable is now missing.

      If I substitute the '=' for something else, it works as expected.

            daspilker Daniel Spilker
            jsniecikowski Jacek Sniecikowski
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: