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

Credentials dropdowns empty when configuring external libraries at the global level

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Adding a "Legacy SCM" git repository.

      The credentials ID drop down does not populate from existing items, nor do new items get added if I add them while editing the configuration.

      Console messages

      These may or may not be relevant (they seem relevant to me)

      hudson-behavior.js:417 Uncaught TypeError: Cannot read property 'firstChild' of undefinedregisterValidator @ hudson-behavior.js:417(anonymous function) @ behavior.js:111(anonymous function) @ behavior.js:107applySubtree @ behavior.js:93(anonymous function) @ select.js:251
      
      hudson-behavior.js:472 Unable to find nearby scm/id
      

      fillCredentialItems

      After adding a new credential item, the following calls were made - it seems like a weird set of items to fill (but I'm not jenkins rpc call savvy) - almost like it wasn't even calling to fill this dropdown.

      http://localhost:8080/descriptorByName/org.jenkinsci.plugins.github.config.HookSecretConfig/fillCredentialsIdItems
      http://localhost:8080/descriptorByName/hudson.plugins.git.UserRemoteConfig/fillCredentialsIdItems
      

        Attachments

          Issue Links

            Activity

            Hide
            hamiltb Bill Hamilton added a comment -

            Mark,
            Thanks, I will wait for git plugin 3.0.1

            Show
            hamiltb Bill Hamilton added a comment - Mark, Thanks, I will wait for git plugin 3.0.1
            Hide
            markewaite Mark Waite added a comment -

            Released in git plugin 3.0.1, 18 Nov 2016

            Show
            markewaite Mark Waite added a comment - Released in git plugin 3.0.1, 18 Nov 2016
            Hide
            hamiltb Bill Hamilton added a comment -

            Mark,
            I just upgraded to Jenkins Git 3.01 (which brought with it Credentials 2.1.9, Jenkins Mailer 1.18, and Jenkins Git client 2.1.0) and a simple "checkout scm" failed with:

            (obfuscated with "-----")
            Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress https://-------/hamiltb/svc-foobar.git +refs/heads/:refs/remotes/origin/" returned status code 128:
            stderr: fatal: cannot exec '/tmp/pass7365890844204257456.sh': Permission denied
            fatal: could not read Username for 'https://-------------': No such device or address

            Show
            hamiltb Bill Hamilton added a comment - Mark, I just upgraded to Jenkins Git 3.01 (which brought with it Credentials 2.1.9, Jenkins Mailer 1.18, and Jenkins Git client 2.1.0) and a simple "checkout scm" failed with: (obfuscated with "-----") Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress https://-------/hamiltb/svc-foobar.git +refs/heads/ :refs/remotes/origin/ " returned status code 128: stderr: fatal: cannot exec '/tmp/pass7365890844204257456.sh': Permission denied fatal: could not read Username for 'https://-------------': No such device or address
            Hide
            markewaite Mark Waite added a comment -

            The message:

            stderr: fatal: cannot exec '/tmp/pass7365890844204257456.sh': Permission denied

            indicates that a file that was written to the /tmp/ directory on the agent that was trying to do the checkout was not made executable. Some possible reasons for it not being made executable might include:

            • Wrong permissions on the /tmp/ directory on the agent (refuses to allow an executable script to run from /tmp)
            • Out of disc space in the /tmp/ directory on the agent (could not write the script to /tmp/)
            • Other file system related oddities on that slave agent

            Since the message:

            fatal: could not read Username for 'https://-------------': No such device or address

            came later in the log, I assume it is a symptom of the earlier message, not the specific message.

            Show
            markewaite Mark Waite added a comment - The message: stderr: fatal: cannot exec '/tmp/pass7365890844204257456.sh': Permission denied indicates that a file that was written to the /tmp/ directory on the agent that was trying to do the checkout was not made executable. Some possible reasons for it not being made executable might include: Wrong permissions on the /tmp/ directory on the agent (refuses to allow an executable script to run from /tmp) Out of disc space in the /tmp/ directory on the agent (could not write the script to /tmp/) Other file system related oddities on that slave agent Since the message: fatal: could not read Username for 'https://-------------': No such device or address came later in the log, I assume it is a symptom of the earlier message, not the specific message.
            Hide
            jglick Jesse Glick added a comment -

            Bill Hamilton better filed & discussed separately, especially if it is reproducible. Off topic in this issue.

            Show
            jglick Jesse Glick added a comment - Bill Hamilton better filed & discussed separately, especially if it is reproducible. Off topic in this issue.

              People

              • Assignee:
                jglick Jesse Glick
                Reporter:
                bwalding Ben Walding
              • Votes:
                17 Vote for this issue
                Watchers:
                31 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: