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

SCM username/password env variables don't work with SECURITY-170

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • m2release-plugin
    • Jenkins LTS 1.651.2, Oracle JDK 8u92, Windows Server 2008R2

      For a Maven job a have SCM username and password environment variables configured. This work with Jenkins LTS v1.651.1 but with v1.651.2 it doesn't. The environment variables don't seem to be set. I suspect that SECURITY-170 fix is the reason for this behavior.
      The plugin needs to be updated to work with this change.

          [JENKINS-35261] SCM username/password env variables don't work with SECURITY-170

          Anders Hammar created issue -
          James Nord made changes -
          Labels New: security-170
          James Nord made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          James Nord made changes -
          Remote Link New: This issue links to "PR 29 (Web Link)" [ 14356 ]
          James Nord made changes -
          Status Original: In Progress [ 3 ] New: Open [ 1 ]
          James Nord made changes -
          Link New: This issue is duplicated by JENKINS-36342 [ JENKINS-36342 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 171502 ] New: JNJira + In-Review [ 184332 ]
          James Nord made changes -
          Assignee Original: James Nord [ teilo ]

            Unassigned Unassigned
            ahammar Anders Hammar
            Votes:
            4 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: