[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mike Kobit commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Has anybody seen this working with recent versions of pipeline plugins and Jenkins? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mike Kobit updated an issue Jenkins / JENKINS-38048 Credentials dropdowns empty when configuring external libraries at the global level Change By: Mike Kobit Comment: Has anybody seen this working with recent versions of pipeline plugins and Jenkins? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Jesse Glick commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Bill Hamilton better filed & discussed separately, especially if it is reproducible. Off topic in this issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mark Waite commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level 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. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Bill Hamilton commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level 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 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mark Waite closed an issue as Fixed Released in git plugin 3.0.1, 18 Nov 2016 Jenkins / JENKINS-38048 Credentials dropdowns empty when configuring external libraries at the global level Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Bill Hamilton commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Mark, Thanks, I will wait for git plugin 3.0.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mark Waite commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level No, your process of tracking plugins is reasonable, but didn't cover the scenario which the git plugin is currently managing. The git plugin delivered a major release (3.0.0) which added submodule authentication. However, the changes needed for submodule authentication were broad enough that they broke compatibility with authentication at some git plugin installations. There are several bugs authentication bugs which have been reported that indicate the changes introduced incompatibilities. This change was applied (and released) in git plugin 2.6.1 in order to retain compatibility with the git plugin 2.x line. It will also be released in the near future as a git plugin 3.0.1. If you need it immediately in released form, and don't need the features added in git plugin 3.0.0, you can download and install 2.6.1 and use it. Otherwise, you can wait a few days and I'll have released the git plugin 3.0.1 version which also includes the fix. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Bill Hamilton commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Hi Mark, CloudBees support showed me how I can take an issue that is marked as fixed (like this one), and go into each of the PRs, and then see what release label contains that fix. So this led me to determining that the above versions of plugins would comprise the fix. And they are available, so I installed them, but it didnt fix it. So was my process of tracking plugin versions incorrect? Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mark Waite commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Fixed but not yet released. A pre-release build is available if you need it faster. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Bill Hamilton commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level I just installed: credentials 2.19 git 3.0 subversion 2.7.0 workflow-cps-global-lib 2.4 restartedand the dropdown is still empty (only contains none). Is this really fixed? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Rishi Goomar commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Mark Waite Any updates on the release for this bug? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mark Waite commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level No, I think it has passed enough of my tests to be released. It should be released before the end of the week. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mike Kobit commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Mark Waite - do you need any assistance in testing/releasing this change? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Jesse Glick updated JENKINS-38048 Jenkins / JENKINS-38048 Credentials dropdowns empty when configuring external libraries at the global level Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/git/UserRemoteConfig.java src/main/java/jenkins/plugins/git/GitSCMSource.java http://jenkins-ci.org/commit/git-plugin/b52b095c8310c607d28120b3a20137eacc58a64c Log: JENKINS-38048 Permits credentialsId dropdowns to be used from a global configuration screen. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Code changed in jenkins User: Jesse Glick Path: src/test/java/hudson/plugins/git/UserRemoteConfigTest.java http://jenkins-ci.org/commit/git-plugin/bf0465f7a8d3f1811c6b458fe1c8f868875b5a6f Log: JENKINS-38048 Proving fix in functional test. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/common/AbstractIdCredentialsListBoxModel.java http://jenkins-ci.org/commit/credentials-plugin/408765b9ad75caf79f8eb03d0b2a524534ed0b64 Log: Merge pull request #68 from jglick/global-credentialsId-JENKINS-38048 JENKINS-38048 Relax nullability on Item/ItemGroup context parameters Compare: https://github.com/jenkinsci/credentials-plugin/compare/abebf76a8f57...408765b9ad75 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/plugins/credentials/common/AbstractIdCredentialsListBoxModel.java http://jenkins-ci.org/commit/credentials-plugin/65e143c42ee9ba7de274482dbf4751e37de8d93d Log: JENKINS-38048 Relax nullability on Item/ItemGroup context parameters. The underlying checks already handle null values. Makes it easier to provide credentials dropdowns in global configuration. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Jesse Glick commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Creating a fake project is definitely not right. Yes I know the declared signature says @Nonnull; refer to credentials PR 68 for why it should be OK anyway. The change worked fine when I developed it, so something must have broken since then. Apparently I will need to revisit the PR. Probably I can add functional tests for it—last I recall there were none is this area. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title
Mark Waite edited a comment on JENKINS-38048
Re: Credentials dropdowns empty when configuring external libraries at the global level
I pushed a change onto my [evaluation branch|https://github.com/MarkEWaite/git-plugin/tree/3.0.0-beta-PR433-PR437-single-revision-and-global-config-credentials-dropdown] which creates a fake project if the project is null. It seems to be well-behaved in the case I tested. However, I suspect that is not the right way to solve the problem.[~jglick], can you provide suggestions of a better way to handle that case?Refer to the [specific diffs|https://github.com/MarkEWaite/git-plugin/commit/91887a000c0082ba7403804fc95cbaf4eebdadf0] for my change.The findbugs analysis also adds a new warning about project potentially being null when the isMatchingAs signature declares it must be non-null (same pattern as in UserRemoteConfig, just needs a different non-null object type) . It says:{code}Null passed for non-null parameter of com.cloudbees.plugins.credentials.common.AbstractIdCredentialsListBoxModel.includeMatchingAs(Authentication, Item, Class, List, CredentialsMatcher) in jenkins.plugins.git.GitSCMSource$DescriptorImpl.doFillCredentialsIdItems(SCMSourceOwner, String, String) [jenkins.plugins.git.GitSCMSource$DescriptorImpl, jenkins.plugins.git.GitSCMSource$DescriptorImpl] Method invoked at GitSCMSource.java:[line 201]Known null at GitSCMSource.java:[line 195]{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title
Mark Waite edited a comment on JENKINS-38048
Re: Credentials dropdowns empty when configuring external libraries at the global level
I pushed a change onto my [evaluation branch|https://github.com/MarkEWaite/git-plugin/tree/3.0.0-beta-PR433-PR437-single-revision-and-global-config-credentials-dropdown] which creates a fake project if the project is null. It seems to be well-behaved in the case I tested. However, I suspect that is not the right way to solve the problem.[~jglick], can you provide suggestions of a better way to handle that case?Refer to the [specific diffs|https://github.com/MarkEWaite/git-plugin/commit/91887a000c0082ba7403804fc95cbaf4eebdadf0] for my change. The findbugs analysis also adds a new warning about project potentially being null when the isMatchingAs signature declares it must be non-null. It says:{code}Null passed for non-null parameter of com.cloudbees.plugins.credentials.common.AbstractIdCredentialsListBoxModel.includeMatchingAs(Authentication, Item, Class, List, CredentialsMatcher) in jenkins.plugins.git.GitSCMSource$DescriptorImpl.doFillCredentialsIdItems(SCMSourceOwner, String, String) [jenkins.plugins.git.GitSCMSource$DescriptorImpl, jenkins.plugins.git.GitSCMSource$DescriptorImpl] Method invoked at GitSCMSource.java:[line 201]Known null at GitSCMSource.java:[line 195]{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mark Waite edited a comment on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level I pushed a change onto my [evaluation branch|https://github.com/MarkEWaite/git-plugin/tree/3.0.0-beta-PR433-PR437-single-revision-and-global-config-credentials-dropdown] which creates a fake project if the project is null. It seems to be well-behaved in the case I tested. However, I suspect that is not the right way to solve the problem.[~jglick], can you provide suggestions of a better way to handle that case? Refer to the [specific diffs|https://github.com/MarkEWaite/git-plugin/commit/91887a000c0082ba7403804fc95cbaf4eebdadf0] for my change. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mark Waite commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level I pushed a change onto my evaluation branch which creates a fake project if the project is null. It seems to be well-behaved in the case I tested. However, I suspect that is not the right way to solve the problem. Jesse Glick, can you provide suggestions of a better way to handle that case? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mark Waite edited a comment on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level I've merged [PR433|https://github.com/jenkinsci/git-plugin/pull/433] and [PR437|https://github.com/jenkinsci/git-plugin/pull/433] to an [evaluation branch|https://github.com/MarkEWaite/git-plugin/tree/3.0.0-beta-PR433-PR437-single-revision-and-global-config-credentials-dropdown] in my repository and am running various tests now to confirm it behaves as expected.I'm able to confirm the bug exists (with a [Jenkins 2.19.1 LTS docker image|https://github.com/MarkEWaite/docker/tree/f70ac08688d0761353430c08a7fafee176894e24], downloading the latest plugins, including git plugin 3.0.0 and git client plugin 2.0.0). When I built a [version of git plugin|https://github.com/MarkEWaite/git-plugin/commit/596907ef61ea3bfce24586ba72492cc6b3fb0c49] which merges the master branch, PR433, and PR437, the credentials drop down still does not populate. The commit history for that shows the [change|https://github.com/MarkEWaite/git-plugin/commit/086896ab4e53e6a98986522d0ddbebf1ad0eaf91] which [~jglick] referenced, but does not show the global credentials drop down.I'll need to do some further debugging to understand what's happening. !empty-global-pipeline-credential-dropdown.png|thumbnail! It seems that the credentials plugin includeMatchingAs() method may not accept a null project, yet in a global context, the project will be null. Is there an alternative to includeMatchingAs() which does not require a project for context? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) --
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mark Waite edited a comment on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level I've merged [PR433|https://github.com/jenkinsci/git-plugin/pull/433] and [PR437|https://github.com/jenkinsci/git-plugin/pull/433] to an [evaluation branch|https://github.com/MarkEWaite/git-plugin/tree/3.0.0-beta-PR433-PR437-single-revision-and-global-config-credentials-dropdown] in my repository and am running various tests now to confirm it behaves as expected.I'm able to confirm the bug exists (with a [Jenkins 2.19.1 LTS docker image|https://github.com/MarkEWaite/docker/tree/f70ac08688d0761353430c08a7fafee176894e24], downloading the latest plugins, including git plugin 3.0.0 and git client plugin 2.0.0). When I built a [version of git plugin|https://github.com/MarkEWaite/git-plugin/commit/596907ef61ea3bfce24586ba72492cc6b3fb0c49] which merges the master branch, PR433, and PR437, the credentials drop down still does not populate. The commit history for that shows the [change|https://github.com/MarkEWaite/git-plugin/commit/086896ab4e53e6a98986522d0ddbebf1ad0eaf91] which [~jglick] referenced, but does not show the global credentials drop down.I'll need to do some further debugging to understand what's happening. !empty-global-pipeline-credential-dropdown.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mark Waite edited a comment on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level I've merged [PR433|https://github.com/jenkinsci/git-plugin/pull/433] and [PR437|https://github.com/jenkinsci/git-plugin/pull/433] to an [evaluation branch|https://github.com/MarkEWaite/git-plugin/tree/3.0.0-beta-PR433-PR437-single-revision-and-global-config-credentials-dropdown] in my repository and am running various tests now to confirm it behaves as expected.I'm able to confirm the bug exists (with a [Jenkins 2.19.1 LTS docker image|https://github.com/MarkEWaite/docker/tree/f70ac08688d0761353430c08a7fafee176894e24], downloading the latest plugins, including git plugin 3.0.0 and git client plugin 2.0.0). When I built a [version of git plugin|https://github.com/MarkEWaite/git-plugin/commit/596907ef61ea3bfce24586ba72492cc6b3fb0c49] which merges the master branch, PR433, and PR437, the credentials drop down still does not populate. The commit history for that shows the [change|https://github.com/MarkEWaite/git-plugin/commit/086896ab4e53e6a98986522d0ddbebf1ad0eaf91] which [~jglick] referenced, but does not show the global credentials drop down.I'll need to do some further debugging to understand what's happening. !empty-global-pipeline-credential-dropdown.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mark Waite edited a comment on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level I've merged [PR433|https://github.com/jenkinsci/git-plugin/pull/433] and [PR437|https://github.com/jenkinsci/git-plugin/pull/433] to an [evaluation branch|https://github.com/MarkEWaite/git-plugin/tree/3.0.0-beta-PR433-PR437-single-revision-and-global-config-credentials-dropdown] in my repository and am running various tests now to confirm it behaves as expected.I'm able to confirm the bug exists (with a [Jenkins 2.19.1 LTS docker image|https://github.com/MarkEWaite/docker/tree/f70ac08688d0761353430c08a7fafee176894e24], downloading the latest plugins, including git plugin 3.0.0 and git client plugin 2.0.0). When I built a [version of git plugin|https://github.com/MarkEWaite/git-plugin/commit/596907ef61ea3bfce24586ba72492cc6b3fb0c49] which merges the master branch, PR433, and PR437, the credentials drop down still does not populate. The commit history for that shows the [change|https://github.com/MarkEWaite/git-plugin/commit/086896ab4e53e6a98986522d0ddbebf1ad0eaf91] which [~jglick] referenced, but does not show the global credentials drop down.I'll need to do some further debugging to understand what's happening. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mark Waite edited a comment on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level I've merged [PR433|https://github.com/jenkinsci/git-plugin/pull/433] and [PR437|https://github.com/jenkinsci/git-plugin/pull/433] to an [evaluation branch|https://github.com/MarkEWaite/git-plugin/tree/3.0.0-beta-PR433-PR437-single-revision-and-global-config-credentials-dropdown] in my repository and am running various tests now to confirm it behaves as expected. I hope 'm able to release confirm the bug exists (with a new [Jenkins 2.19.1 LTS docker image|https://github.com/MarkEWaite/docker/tree/f70ac08688d0761353430c08a7fafee176894e24], downloading the latest plugins, including git plugin 3.0.0 and git client plugin 2.0.0). When I built a [ version of git plugin|https://github.com/MarkEWaite/git-plugin/commit/596907ef61ea3bfce24586ba72492cc6b3fb0c49] which merges the master branch, PR433, and PR437, the credentials drop down still does not populate. The commit history for that shows the [change|https://github.com/MarkEWaite/ git - plugin with those changes in a week or less /commit/086896ab4e53e6a98986522d0ddbebf1ad0eaf91] which [~jglick] referenced, but does not show the global credentials drop down . I'll need to do some further debugging to understand what's happening. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-38048 Credentials dropdowns empty when configuring external libraries at the global level Change By: Mark Waite Attachment: empty-global-pipeline-credential-dropdown.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mark Waite commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level I've merged PR433 and PR437 to an evaluation branch in my repository and am running various tests now to confirm it behaves as expected. I hope to release a new version of the git plugin with those changes in a week or less. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Jesse Glick commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Mercurial needs some more work, which I have lumped into JENKINS-35535. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Jesse Glick commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level For Subversion users this is now fixed in 2.7.1. For Git, ping Mark Waite. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mike Kobit edited a comment on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Still Git is still waiting on https://github.com/jenkinsci/git-plugin/pull/437, really looking forward to not having to use Chrome Editor tools to use this feature . ! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mike Kobit commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Still waiting on https://github.com/jenkinsci/git-plugin/pull/437, really looking forward to not having to use Chrome Editor tools to use this feature. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/hudson/scm/SubversionSCM.java src/main/java/hudson/scm/SubversionTagAction.java src/main/java/hudson/scm/browsers/Sventon.java src/main/java/hudson/scm/browsers/Sventon2.java src/main/java/jenkins/scm/impl/subversion/SubversionSCMSource.java http://jenkins-ci.org/commit/subversion-plugin/1355c64e36933049fcb3c2f50cc3eaf189cef241 Log: JENKINS-38048 Permits credentialsId dropdowns to be used from a global configuration screen. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Code changed in jenkins User: Manuel Recena Path: pom.xml src/main/java/hudson/scm/SubversionSCM.java src/main/java/hudson/scm/SubversionTagAction.java src/main/java/hudson/scm/browsers/Sventon.java src/main/java/hudson/scm/browsers/Sventon2.java src/main/java/jenkins/scm/impl/subversion/SubversionSCMSource.java http://jenkins-ci.org/commit/subversion-plugin/ca23e9fa4b4f3bdac4112f1157cfc9efe303d3f7 Log: Merge pull request #169 from jglick/global-credentialsId-JENKINS-38048 JENKINS-38048 Permit credentialsId dropdowns to be used from a global configuration screen Compare: https://github.com/jenkinsci/subversion-plugin/compare/3159d9a64e23...ca23e9fa4b4f Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Alan Ranciato commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Anton Lundin - THANK YOU! I didn't catch the answer b/c I didn't think there was any way that was the actual fix... I feel dirty after doing it, but your fix works and gave me what I needed to move forward. Someday, maybe, the PRs will get accepted and we won't have to do this... Until then, THANK YOU for your assistance! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Anton Lundin commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level I used devtoos in chrome to change the page. If you don't know how to do that this ain't the support forum for that. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Alan Ranciato commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Anton Lundin sorry for my ignorance - where Are the html files located that you're modifying? I assume you are doing this post - compile on your running version? Thx Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Anton Lundin commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Edit the select drop down and just add the inside the containing the right credentials. You can copy the options tag from a working svn configuration page. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Alan Ranciato commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Anton Lundin - Can you provide more details of your workaround? I like the way it sounds. I am using the Multibranch pipeline plugin so I don't have the option of getting around the sandbox so my only option to perform anything somewhat complex (Artifactory Maven builds for example) is the global pipeline library so I have something trusted. The lack of credentials in stopping me from moving forward. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Roy Tinker commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level The workaround seemed to work, but then I got E200015: ISVNAuthentication provider did not provide credentials. I decided to dodge global pipeline libraries altogether and just checkout from SVN and load the pipeline library file directly. Here's what that looks like: https://gist.github.com/RoyTinker/69d0f1b962cb91336db4d2180934af3e Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Anton Lundin commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level I'm running into this issue to. I worked around it by modifying the html of the configure page in devtools, adding the credeltials to the dropdown and it now works. I use Legacy Subversion over http. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Dayton Gomez commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level I've also tried the workaround using SSH, and it didn't work either. Simply gave me an auth error and bailed out. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Marcus Philip commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Hendrik Brinkmann I use http protocol indeed, so Jesse Glick the question is still open: Did you actually get that workaround to work. I cannot. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Roy Tinker commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Related (or redundant) issue: https://issues.jenkins-ci.org/browse/JENKINS-38424 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title
Hendrik Brinkmann edited a comment on JENKINS-38048
Re: Credentials dropdowns empty when configuring external libraries at the global level
Your git-url starts with {{https://}}. Is your credential a username with password or a private ssh-key . ? If the latter applied, I would expect an url that starts with {{ssh://}}{code:xml} https://git.netent.com/scm/ngp/jenkins-workflow-libs.git{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Hendrik Brinkmann commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Your Git-Url starts with https://. Is your credential a username with password or a private ssh-key. If the latter applied, I would expect an url that starts with ssh:// https://git.netent.com/scm/ngp/jenkins-workflow-libs.git Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title
Hendrik Brinkmann edited a comment on JENKINS-38048
Re: Credentials dropdowns empty when configuring external libraries at the global level
Your Git git - Url url starts with {{https://}}. Is your credential a username with password or a private ssh-key. If the latter applied, I would expect an url that starts with {{ssh://}}{code:xml} https://git.netent.com/scm/ngp/jenkins-workflow-libs.git{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title
Marcus Philip commented on JENKINS-38048
Re: Credentials dropdowns empty when configuring external libraries at the global level
Jesse Glick I cannot get your workaround to work: I have added credentialsId to org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml:
"workflow-cps-global-lib@2.3">
netentNGPCoreLib
"org.jenkinsci.plugins.workflow.libs.SCMRetriever">
"hudson.plugins.git.GitSCM" plugin="git@3.0.0">
2
https://git.netent.com/scm/ngp/jenkins-workflow-libs.git
myCredentialsId
refs/heads/${library.netentNGPCoreLib.version}
...
and run 'Reload Configuration from Disk', but I still get error:
Loading library netentNGPCoreLib@master
> /opt/rh/git19/root/usr/bin/git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> /opt/rh/git19/root/usr/bin/git config remote.origin.url https://git.netent.com/scm/ngp/jenkins-workflow-libs.git # timeout=10
Fetching upstream changes from https://git.netent.com/scm/ngp/jenkins-workflow-libs.git
> /opt/rh/git19/root/usr/bin/git --version # timeout=10
> /opt/rh/git19/root/usr/bin/git fetch --tags --progress https://git.netent.com/scm/ngp/jenkins-workflow-libs.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from https://git.netent.com/scm/ngp/jenkins-workflow-libs.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1051)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1082)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109)
at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.doRetrieve(SCMSourceRetriever.java:102)
at org.jenkinsci.plugins.workflow.libs.SCMRetriever.retrieve(SCMRetriever.java:58)
at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:150)
at org.jenkinsci.plugins.workflow.libs.LibraryAdder.add(LibraryAdder.java:131)
at org.jenkinsci.plugins.workflow.libs.LibraryDecorator$1.call(LibraryDecorator.java:99)
at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:970)
at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:548)
at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:526)
at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:503)
at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:302)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:281)
at groovy.lang.GroovyShell.parseClass(GroovyShell.java:731)
at groovy.lang.GroovyShell.parse(GroovyShell.java:743)
at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:410)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:373)
at
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Marcus Philip commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level I think JENKINS-38272 is a duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Jesse Glick commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level add the credentialsId to the xml config Specifically should look like something-here where the ID would either be something you picked when creating the credentials, or a generated UUID. The exact placement will depend on the SCM, so you need to consult an example of a freestyle project configuration. the legacy git provider won't do substitution Yes it does; this is tested. I suspect you mistyped the library name in the variable. why I can not anymore select globally defined credentials from the dropdown Not sure what you are referring to. This issue only refers to a lack of support for credentials dropdowns in a newly added feature, Pipeline library definitions in the global system configuration. Anything else is unrelated. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Gunter Grodotzki commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Is this also the reason why I can not anymore select globally defined credentials from the dropdown (git plugin) ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title
Ben Walding commented on JENKINS-38048
Re: Credentials dropdowns empty when configuring external libraries at the global level
I was able to add the credentialsId to the xml config and reload to get me past this problem. It also seems that the legacy git provider won't do substitution of $ {library.cloudbees-jenkins-ops-library.version} into the branch specifier. But I'll wait for the rest of the fixes to go through before I investigate that more thoroughly. I worked around that by hardcoding the version into the library. e.g.
> git rev-parse refs/remotes/origin/${library.app.version}^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/${library.app.version}^{commit} # timeout=10
> git rev-parse origin/${library.app.version}^{commit} # timeout=10
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38048 Credentials dropdowns empty when configuring external libraries at the global level Change By: Jesse Glick Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38048 Credentials dropdowns empty when configuring external libraries at the global level Change By: Jesse Glick Summary: credentials id dropdown not populated Credentials dropdowns empty when configuring external libraries at the global level Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
