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

CasC ciphers values already ciphered when running under test

    Details

    • Similar Issues:

      Description

      Jenkins 2.73.3, 2.164.1, 2.165 when running " under test ", let's say `mvn hpi:run` or `mvn test`, ciphers the tokens even though they are ciphered in the YAML, whereas the same Jenkins running normally doesn't cipher the tokens if they are already ciphered.

      When configuring with the attached yml:

      If Jenkins is running normally (java -jar ...), in the viewExport page (View Configuration button) it shows:

      _

      {AQAAABAAAAAQ93qR7ipIm+dYmOZ1AXqSLWDj9V+KUrHew/fiyPNoHTo=}

      _

      The same as in the file.

      But when running under test, with mvn hpi:run or running integration tests (mvn package) it shows:

      usernamePassword:
      _

      {AQAAABAAAABA1e/z7rT6SsbMm5XmaDkHn0N8YeoHYRm8JltNZh68IZumi/SmbDrI+nH8Z51YNwSokbUbxkq85QMMe5CkEDLL+YNkXGcnAMwvSgTLLH71dlc=}

      _
       
      basicSSHUserPrivateKey:
      _

      {AQAAABAAAABAb5Y+gVJlthgpEfLXRvFmnYtPqeTnxFDzNaKpRPDhpbWw70t7h4W1jI9h5u7TEafPxk6AhWmq+BoWkzAQtKLvzYFLCUwE2xNusw5nXeKVklY=}

      _
       
      Even though both secrets are the same in the yaml file. Not sure if it's expected.

        Attachments

          Activity

          Show
          mramonleon Ramon Leon added a comment - https://github.com/jenkinsci/configuration-as-code-plugin/issues/913

            People

            • Assignee:
              ewel Ewelina Wilkosz
              Reporter:
              mramonleon Ramon Leon
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: