[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm

Issue Type:	Bug
Assignee:	stephenconnolly
Components:	credentials-plugin, git-client-plugin, git-plugin
Created:	2016/Sep/12 8:30 AM
Environment:	Jenkins 2.7.4 (LTS)
Priority:	Minor
Reporter:	Gunter Grodotzki

Since recently (might be through the 2.7.3 to 2.7.4 upgrade) I am unable to select any credentials with the git settings directly in the job configuration.

Even if I add credentials, it does not show in the list.

Any advices?

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

gunter@grodotzki.co.za (JIRA)

unread,

Sep 12, 2016, 5:07:01 AM9/12/16

to jenkinsc...@googlegroups.com

Gunter Grodotzki updated an issue

Jenkins /

Change By:	Gunter Grodotzki

Since recently (might be through the 2.7.3 to 2.7.4 upgrade) I am unable to select any credentials with the git settings directly in the job configuration.

Even if I add credentials, it does not show in the list.

Any advices?

{code}
$ java -version
java version "1.8.0_102"
Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)
{code}

{code}
$ git --version
git version 1.9.1
{code}

{code}
Ubuntu 14.04 LTS latest apt update && apt upgrade
{code}

mark.earl.waite@gmail.com (JIRA)

unread,

Sep 12, 2016, 7:03:04 AM9/12/16

to jenkinsc...@googlegroups.com

Mark Waite commented on

It will be a great help if you can isolate the component upgrade which actually caused the change.

The git plugin switched from using credentials 1.x to credentials 2.1 as part of the change from git plugin 2.5.3 to 2.6.0. If you're running git plugin 2.6.0 and you downgrade to an earlier version, do the credentials again appear?

gunter@grodotzki.co.za (JIRA)

unread,

Sep 12, 2016, 7:45:01 AM9/12/16

to jenkinsc...@googlegroups.com

Gunter Grodotzki commented on

I downgraded to the following versions, unfortunately no luck:

Credentials Plugin: 2.1.0
Git client plugin: 1.21.0
Git plugin: 2.6.0

As far as I can remember though there was a major git/credentials upgrade recently? E.g. the above versions where when the problems started (which was right after I upgraded Jenkins to 2.7.4) - the git 3.0.0 / git-client 2.0.0 only came a few days afterwards which I was hoping would fix the issue.

I actually did now a manual install of the Git plugin 2.5.3 (http://updates.jenkins-ci.org/download/plugins/git/2.5.3/git.hpi) - and my creds are back!

I am curious why I am the only one having this issue and if there is something else maybe actually going wrong?

gunter@grodotzki.co.za (JIRA)

unread,

Sep 12, 2016, 7:46:02 AM9/12/16

to jenkinsc...@googlegroups.com

Gunter Grodotzki edited a comment on

I downgraded to the following versions, unfortunately no luck:

* Credentials Plugin: 2.1.0
* Git client plugin: 1.21.0
* Git plugin: 2.6.0

As far as I can remember though there was a major git/credentials upgrade recently? E.g. the above versions where when the problems started (which was right after I upgraded Jenkins to 2.7.4) - the git 3.0.0 / git-client 2.0.0 only came a few days afterwards which I was hoping would fix the issue.

I actually did now However, after doing a manual install of the Git plugin 2.5.3 (http://updates.jenkins-ci.org/download/plugins/git/2.5.3/git.hpi) - and my creds are back!

I am curious why I am the only one having this issue and if there is something else maybe actually going wrong?

gunter@grodotzki.co.za (JIRA)

unread,

Sep 12, 2016, 7:50:01 AM9/12/16

to jenkinsc...@googlegroups.com

Gunter Grodotzki edited a comment on

I downgraded to the following versions, unfortunately no luck:

* Credentials Plugin: 2.1.0
* Git client plugin: 1.21.0
* Git plugin: 2.6.0

As far as I can remember though there was a major git/credentials upgrade recently? E.g. the above versions where when the problems started (which was right after I upgraded Jenkins to 2.7.4) - the git 3.0.0 / git-client 2.0.0 only came a few days afterwards which I was hoping would fix the issue.

However, after doing a manual install of the Git plugin 2.5.3 (http://updates.jenkins-ci.org/download/plugins/git/2.5.3/git.hpi) - and * my creds are back! *

I am curious why I am the only one having this issue and if there is something else maybe actually going wrong?

gunter@grodotzki.co.za (JIRA)

unread,

Sep 12, 2016, 7:52:02 AM9/12/16

to jenkinsc...@googlegroups.com

Gunter Grodotzki edited a comment on

I downgraded to the following versions, unfortunately no luck:

* Credentials Plugin: 2.1.0
* Git client plugin: 1.21.0
* Git plugin: 2.6.0

As far as I can remember though there was a major git/credentials upgrade recently? E.g. the above versions where when the problems started (which was right after I upgraded Jenkins to 2.7.4) - the git 3.0.0 / git-client 2.0.0 only came a few days afterwards which I was hoping would fix the issue.

However, after doing a manual install of the Git plugin 2.5.3 (http://updates.jenkins-ci.org/download/plugins/git/2.5.3/git.hpi) - *my creds are back!*

I am curious why I am the only one having this issue and if there is something else maybe actually going wrong?

Update: fwiw, on another setup with Jenkins 2.11 I am not having the issue - e.g. everything works with latest git/cred plugins. However there are also only a handful of plugins installed..

mark.earl.waite@gmail.com (JIRA)

unread,

Sep 15, 2016, 11:34:01 AM9/15/16

to jenkinsc...@googlegroups.com

Mark Waite commented on

I don't know why you're seeing that behavior. Are there any other differences you've detected between the working environment and the broken environment?

gunter@grodotzki.co.za (JIRA)

unread,

Sep 15, 2016, 12:49:03 PM9/15/16

to jenkinsc...@googlegroups.com

Gunter Grodotzki commented on

The working environment is completely different:

far less plugins installed
did not upgrade from the 1.xx, but was a fresh 2.x installation
far less jobs configured

I will try to replicate it on a VBox.

arnaud.lamy@gmail.com (JIRA)

unread,

Sep 17, 2016, 4:36:01 PM9/17/16

to jenkinsc...@googlegroups.com

arnaud lamy commented on

@Gunter For info I can reproduce it with docker image: jenkins:2.7.4

mark.earl.waite@gmail.com (JIRA)

unread,

Sep 17, 2016, 9:35:02 PM9/17/16

to jenkinsc...@googlegroups.com

Mark Waite commented on

arnaud lamy can you give more details of the steps you take to reproduce the problem with the docker image jenkins:2.7.4? I tried the following steps and was unable to see the issue:

Run docker image jenkins:2.7.4 from dockerhub with the command docker run --rm -i --dns 8.8.8.8 --publish 9090:8080 -t jenkins:2.7.4, note the initial login password presented in the window where docker was started,
Open web browser to http://localhost:9090/
Paste the initial login password into the web browser
Select the "Install recommended plugins" box, wait for plugins to install
Complete the "Create First Admin User" form with my login information
Click the "Start using Jenkins" button
Click the "Credentials" link on the left side of the screen
Click the "Jenkins" credentials scope to open the Jenkins credentials scope
Click the "Global credentials" link to open the global credentials folder
Click "Add Credentials" to add a credential
Enter my github username and personal access token and save that credential
Create a new freestyle job named "bin"
Use Git as the SCM with the URL https://github.com/MarkEWaite//bin and the credential I previously defined (selected from the pick list)
Run the job and confirm that the username / password credential works for that job as expected

mark.earl.waite@gmail.com (JIRA)

unread,

Sep 17, 2016, 9:37:03 PM9/17/16

to jenkinsc...@googlegroups.com

Mark Waite edited a comment on

[~arnaudlamy] can you give more details of the steps you take to reproduce the problem with the docker image jenkins:2.7.4? I tried the following steps and was unable to see the issue:

# Run docker image jenkins:2.7.4 from dockerhub with the command {{docker run --rm -i --dns 8.8.8.8 --publish 9090:8080 -t jenkins:2.7.4}}, note record the initial login password presented in from the window where docker was started ,
# Open web browser to http://localhost:9090/
# Paste the initial login password into the web browser
# Select the "Install recommended plugins" box, wait for plugins to install
# Complete the "Create First Admin User" form with my login information
# Click the "Start using Jenkins" button
# Click the "Credentials" link on the left side of the screen
# Click the "Jenkins" credentials scope to open the Jenkins credentials scope
# Click the "Global credentials" link to open the global credentials folder
# Click "Add Credentials" to add a credential
# Enter my github username and personal access token and save that credential
# Create a new freestyle job named "bin"
# Use Git as the SCM with the URL https://github.com/MarkEWaite//bin and the credential I previously defined (selected from the pick list)
# Run the job and confirm that the username / password credential works for that job as expected

mark.earl.waite@gmail.com (JIRA)

unread,

Sep 17, 2016, 9:37:03 PM9/17/16

to jenkinsc...@googlegroups.com

Mark Waite edited a comment on

[~arnaudlamy] can you give more details of the steps you take to reproduce the problem with the docker image jenkins:2.7.4? I tried the following steps and was unable to see the issue:

# Run docker image jenkins:2.7.4

{ { noformat}

docker run --rm -i --dns 8.8.8.8 --publish 9090:8080 -t jenkins:2.7.4

{noformat } }
, record the initial login password from the window,

# Open web browser to http://localhost:9090/
# Paste the initial login password into the web browser
# Select the "Install recommended plugins" box, wait for plugins to install
# Complete the "Create First Admin User" form with my login information
# Click the "Start using Jenkins" button
# Click the "Credentials" link on the left side of the screen
# Click the "Jenkins" credentials scope to open the Jenkins credentials scope
# Click the "Global credentials" link to open the global credentials folder
# Click "Add Credentials" to add a credential
# Enter my github username and personal access token and save that credential
# Create a new freestyle job named "bin"
# Use Git as the SCM with the URL https://github.com/MarkEWaite//bin and the credential I previously defined (selected from the pick list)
# Run the job and confirm that the username / password credential works for that job as expected

mark.earl.waite@gmail.com (JIRA)

unread,

Sep 17, 2016, 9:40:02 PM9/17/16

to jenkinsc...@googlegroups.com

I did not apply any limiting conditions to the visibility of those credentials. Maybe you had some additional configuration steps that are relevant?

arnaud.lamy@gmail.com (JIRA)

unread,

Sep 18, 2016, 6:00:01 AM9/18/16

to jenkinsc...@googlegroups.com

arnaud lamy commented on

Indeed I forgot one important element sorry about that. I provided to my docker an old jenkins folder (1.5.X). Here's my command:

`docker run --user=jenkins -p 8081:8080 -p 50000:50000 -d --name jenkins --restart always -v /home/jenkins/docker_var:/var/jenkins_home jenkins:$

{VERSION}

`

One other thing, I installed gitlab auth system plugin and then restarted Jenkins and credential are listed now !

arnaud.lamy@gmail.com (JIRA)

unread,

Sep 18, 2016, 6:01:01 AM9/18/16

to jenkinsc...@googlegroups.com

arnaud lamy edited a comment on

Indeed I forgot one important element sorry about that. I provided to my docker an old jenkins folder (1.5.X). Here's my command:

`

{code:bash}

docker run --user=jenkins -p 8081:8080 -p 50000:50000 -d --name jenkins --restart always -v /home/jenkins/docker_var:/var/jenkins_home jenkins:${VERSION} `

{code}

One other thing, I installed gitlab auth system plugin and then restarted Jenkins and credential are listed now !

arnaud.lamy@gmail.com (JIRA)

unread,

Sep 18, 2016, 6:01:06 AM9/18/16

to jenkinsc...@googlegroups.com

arnaud lamy edited a comment on

Indeed I forgot one important element sorry about that. I provided to my docker an old jenkins folder (1.5.X). Here's my command:

{code: bash none }

docker run --user=jenkins -p 8081:8080 -p 50000:50000 -d --name jenkins --restart always -v /home/jenkins/docker_var:/var/jenkins_home jenkins:${VERSION}
{code}

One other thing, I installed gitlab auth system plugin and then restarted Jenkins and credential are listed now !

arnaud.lamy@gmail.com (JIRA)

unread,

Sep 18, 2016, 6:02:01 AM9/18/16

to jenkinsc...@googlegroups.com

arnaud lamy edited a comment on

Indeed I forgot one important element sorry about that. I provided to my docker an old jenkins folder (1.5.X). Here's my command:

{code:none}

docker run --user=jenkins -p 8081:8080 -p 50000:50000 -d --name jenkins --restart always -v /home/jenkins/docker_var:/var/jenkins_home jenkins:${VERSION}
{code}

One other thing, I installed gitlab auth system plugin and then restarted Jenkins and credential credentials are listed now !

arnaud.lamy@gmail.com (JIRA)

unread,

Sep 18, 2016, 6:04:04 AM9/18/16

to jenkinsc...@googlegroups.com

arnaud lamy edited a comment on

Indeed I forgot one important element sorry about that. I provided to my docker an old jenkins folder (1.5.X). Here's my command:

{code:none}
docker run --user=jenkins -p 8081:8080 -p 50000:50000 -d --name jenkins --restart always -v /home/jenkins/docker_var:/var/jenkins_home jenkins:${VERSION}
{code}

One other thing Then I follow the procedure and installed recommanded plugin as well. Then I create a new project , select GIT and click on add to create a new credential. Impossible to list them.

Since then, I installed gitlab auth system plugin and then restarted Jenkins and credentials are listed now !

mark.earl.waite@gmail.com (JIRA)

unread,

Sep 18, 2016, 10:14:06 AM9/18/16

to jenkinsc...@googlegroups.com

Mark Waite commented on

arnaud lamy it seems that you were able to resolve the issue by updating an unrelated plugin and restarting Jenkins. I thought that Gunter Grodotzki described that a Jenkins restart was not enough to resolve the problem when he saw it. Can you confirm that restarting Jenkins resolves it for you?

arnaud.lamy@gmail.com (JIRA)

unread,

Sep 18, 2016, 10:34:01 AM9/18/16

to jenkinsc...@googlegroups.com

arnaud lamy commented on

Yes it does, do you want that I restart from scratch the test without specifying the old Jenkins folder to my docker?

mark.earl.waite@gmail.com (JIRA)

unread,

Sep 18, 2016, 10:37:02 AM9/18/16

to jenkinsc...@googlegroups.com

Mark Waite commented on

Yes, since that would confirm that the problem is not visible from a freshly installed Jenkins, only from a Jenkins which has been upgraded from a previous version. My testing is biased (by my docker repository) towards testing fresh installations, so an upgrade related bug needs more careful thought and more test automation to identify the issue and confirm it is fixed.

mark.earl.waite@gmail.com (JIRA)

unread,

Sep 18, 2016, 10:38:03 AM9/18/16

to jenkinsc...@googlegroups.com

Mark Waite edited a comment on

Yes, since that would confirm that the problem is not visible from a freshly installed Jenkins, only from a Jenkins which has been upgraded from a previous version. My testing is biased (by my docker repository) towards testing fresh installations, so an upgrade related bug needs more careful thought and more test automation to identify the issue and confirm it is fixed.

It would also be a great help if you could provide any hints on what in the older configuration makes it susceptible to this bug.

mark.earl.waite@gmail.com (JIRA)

unread,

Sep 18, 2016, 10:39:01 AM9/18/16

to jenkinsc...@googlegroups.com

Mark Waite edited a comment on

Yes, since that would confirm that the problem is not visible from a freshly installed Jenkins, only from a Jenkins which has been upgraded from a previous version. My testing is biased (by my docker repository) towards testing fresh installations, so an upgrade related bug needs more careful thought and more test automation to identify the issue and confirm it is fixed.

It would also be a great help if you could provide any hints on what in the older configuration makes it susceptible to this bug. I hope that [~lifeofguenter] could provide similar information.

arnaud.lamy@gmail.com (JIRA)

unread,

Sep 18, 2016, 1:33:02 PM9/18/16

to jenkinsc...@googlegroups.com

arnaud lamy commented on

I restart the test from scratch and everything is fine, I confirm it was due to my old folder to upgrade.

gunter@grodotzki.co.za (JIRA)

unread,

Sep 22, 2016, 7:41:02 PM9/22/16

to jenkinsc...@googlegroups.com

Gunter Grodotzki commented on

Mark Waite: I restarted jenkins and the server multiple times - did not help. Also we already upgraded from 1.X LTS to 2.X LTS a longer time ago.

mark.earl.waite@gmail.com (JIRA)

unread,

Sep 22, 2016, 7:46:03 PM9/22/16

to jenkinsc...@googlegroups.com

Mark Waite commented on

Gunter Grodotzki thanks for the clarification. Unfortunately, I can't duplicate the problem you're seeing. If you can find a way to allow others to duplicate the problem, it makes it much more likely that a fix could be made.

stephenconnolly@java.net (JIRA)

unread,

Oct 3, 2016, 12:09:03 PM10/3/16

to jenkinsc...@googlegroups.com

stephenconnolly updated an issue

Jenkins /

Change By:	stephenconnolly
Component/s:	credentials-plugin

stephenconnolly@java.net (JIRA)

unread,

Oct 3, 2016, 12:09:04 PM10/3/16

to jenkinsc...@googlegroups.com

stephenconnolly assigned an issue to Mark Waite

Jenkins /

Change By:	stephenconnolly
Assignee:	stephenconnolly Mark Waite

mark.earl.waite@gmail.com (JIRA)

unread,

Oct 3, 2016, 12:21:02 PM10/3/16

to jenkinsc...@googlegroups.com

Mark Waite assigned an issue to Unassigned

Jenkins /

Change By:	Mark Waite
Assignee:	Mark Waite

gunter@grodotzki.co.za (JIRA)

unread,

Oct 12, 2016, 7:09:01 AM10/12/16

to jenkinsc...@googlegroups.com

Gunter Grodotzki commented on

I just upgraded to latest Jenkins ver. 2.19.1 + updated all plugins - this is still a issue.

Anyone any idea how to resolve this problem, or how to further debug this?

athyagara@yahoo.com (JIRA)

unread,

Oct 17, 2016, 3:12:05 AM10/17/16

to jenkinsc...@googlegroups.com

Thyagarajulu Atthipatla commented on

I also have same issue. I had setup my jenkins with master container,plugin container and data volume using Rancher. I tried all combinations mentioned above with no luck.
I had installed 2.19.1 , 2.7.1 ,1.653.1 and nothing works.
What I noticed is, with github plugin in global configuration, the credentials do appear. where as while creating project/job it doesn't load. Is there something wrong that Iam doing here?
Regards
Thyaga

mark.earl.waite@gmail.com (JIRA)

unread,

Oct 17, 2016, 7:56:04 AM10/17/16

to jenkinsc...@googlegroups.com

Mark Waite commented on

Thyagarajulu Atthipatla since you have it in a container, can you duplicate the problem in a container that could be shared publicly? I can't duplicate the problem, and a publicly accessible container which shows the problem repeatably might make it much easier to diagnose.

athyagara@yahoo.com (JIRA)

unread,

Oct 18, 2016, 1:37:02 PM10/18/16

to jenkinsc...@googlegroups.com

Thyagarajulu Atthipatla commented on

Mark Waite I used rancher catalog to create the jenkins instance.
here is the docker and rancher compose details
docker
jenkins-plugins:
image: rancher/jenkins-plugins:v0.1.1
jenkins-datavolume:
labels:
io.rancher.container.start_once: 'true'
entrypoint:

chown
-R
1000:1000
/var/jenkins_home
image: busybox
volumes:
/var/lib/docker/jenkins-cicd:/var/jenkins_home
jenkins-primary:
ports:
8080:8080/tcp
labels:
io.rancher.sidekicks: jenkins-plugins,jenkins-datavolume
io.rancher.container.hostname_override: container_name
entrypoint:
/usr/share/jenkins/rancher/jenkins.sh
image: jenkins:2.19.1
volumes_from:
jenkins-plugins
jenkins-datavolume
rancher
jenkins-plugins:
scale: 1
metadata:
plugins: |2+

jenkins-datavolume:
scale: 1
metadata:
plugins: |2+

jenkins-primary:
scale: 1
metadata:
plugins: |2+

paul@symphony.com (JIRA)

unread,

Nov 8, 2016, 7:46:02 PM11/8/16

to jenkinsc...@googlegroups.com

Paul Pollack updated an issue

Jenkins /

Change By:	Paul Pollack
Attachment:	Screen Shot 2016-11-08 at 6.58.49 PM.png
Attachment:	Screen Shot 2016-11-08 at 7.00.17 PM.png
Attachment:	Screen Shot 2016-11-08 at 7.13.46 PM.png

paul@symphony.com (JIRA)

unread,

Nov 8, 2016, 7:48:01 PM11/8/16

to jenkinsc...@googlegroups.com

Paul Pollack commented on

I am having the same problem...this is quite frustrating. I see no errors in the log file.

Interestingly, on the same view (configure system) my credentials are showing up. Looks like a bug, no?

Here's a shot of my installed github plugins:

k.hansson.aspman@gmail.com (JIRA)

unread,

Nov 17, 2016, 10:47:05 AM11/17/16

to jenkinsc...@googlegroups.com

Kristofer Hansson Aspman commented on

Same problem here. Git plugin v3.0.0 and Jenkins 2.19.1

mark.earl.waite@gmail.com (JIRA)

unread,

Nov 17, 2016, 6:43:01 PM11/17/16

to jenkinsc...@googlegroups.com

Mark Waite commented on

A pre-release build of the 3.0.1 release of the git plugin is available if you'd like to try it. It includes the fix for this problem.

k.hansson.aspman@gmail.com (JIRA)

unread,

Nov 18, 2016, 4:20:01 AM11/18/16

to jenkinsc...@googlegroups.com

Kristofer Hansson Aspman updated an issue

Jenkins /

Change By:	Kristofer Hansson Aspman
Attachment:	Screenshot 2016-11-18 10.17.39.png

k.hansson.aspman@gmail.com (JIRA)

unread,

Nov 18, 2016, 4:22:01 AM11/18/16

to jenkinsc...@googlegroups.com

Kristofer Hansson Aspman commented on

I tried it now (and restarted Jenkins) but unfortunately, the problem is still there. Like Paul Pollack, I can see the credentials properly in the system configuration but not on job configuration.

mark.earl.waite@gmail.com (JIRA)

unread,

Nov 18, 2016, 8:05:07 AM11/18/16

to jenkinsc...@googlegroups.com

Mark Waite commented on

Kristofer Hansson Aspman and Paul Pollack I am unable to duplicate the problem you're seeing. Can you provide more details about the conditions when you see the problem. Steps I checked:

Global Pipeline Credentials (as fixed by Jesse Glick's PR437)

Add a global pipeline library named "globalPipelineLibraryMarkEWaiteprivate"
Configure the global pipeline library "globalPipelineLibraryMarkEWaiteprivate" to use git as "Legacy SCM"
Click the credentials drop down before entering any URL, confirm all credentials appear
Enter a private URL in the "Repository URL" field
Click the credentials drop down after entering the URL, confirm only credentials for that private repository appear
Observe that intentionally invalid credentials for that private repository can be selected but show red text that they don't authorize access to that private repository
Observe that valid credentials for that private repository do not show red text when they are selected

Job Credentials

Define a new job "JENKINS-38126-credentials-dropdown-empty"
Use Git as the SCM for that job
Confirm that the credentials dropdown for the job shows all credentials prior to entering any repository URL
Enter a repository URL
Confirm that the credentials dropdown for the job shows only credentials matching that repository URL (I checked with a private github.com URL and a private bitbucket.org URL)
Save the job
Confirm that the job runs successfully (clones from the private repository, etc.)

Fresh Install and Job Credentials

Refer to my earlier comment

Could you explain further what you are seeing? Specifically, I'm not clear on the steps you took so that you could

see the credentials properly in the system configuration but not on job configuration

.

mark.earl.waite@gmail.com (JIRA)

unread,

Nov 18, 2016, 8:05:09 AM11/18/16

to jenkinsc...@googlegroups.com

mark.earl.waite@gmail.com (JIRA)

unread,

Nov 18, 2016, 8:06:04 AM11/18/16

to jenkinsc...@googlegroups.com

Mark Waite edited a comment on

[~kralleman] and [~paul_symphony] I am unable to duplicate the problem you're seeing. Can you provide more details about the conditions when you see the problem. Steps I checked:

h3. Global Pipeline Credentials (as fixed by Jesse Glick's [PR437|https://github.com/jenkinsci/git-plugin/pull/437] for JENKINS-38048 )

# Add a global pipeline library named "globalPipelineLibraryMarkEWaiteprivate"
# Configure the global pipeline library "globalPipelineLibraryMarkEWaiteprivate" to use git as "Legacy SCM"
# Click the credentials drop down before entering any URL, confirm all credentials appear
# Enter a private URL in the "Repository URL" field
# Click the credentials drop down after entering the URL, confirm only credentials for that private repository appear
# Observe that intentionally invalid credentials for that private repository can be selected but show red text that they don't authorize access to that private repository
# Observe that valid credentials for that private repository do not show red text when they are selected

h3. Job Credentials

# Define a new job "JENKINS-38126-credentials-dropdown-empty"
# Use Git as the SCM for that job
# Confirm that the credentials dropdown for the job shows all credentials prior to entering any repository URL
# Enter a repository URL
# Confirm that the credentials dropdown for the job shows only credentials matching that repository URL (I checked with a private github.com URL and a private bitbucket.org URL)
# Save the job
# Confirm that the job runs successfully (clones from the private repository, etc.)

h3. Fresh Install and Job Credentials

# Refer to my [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-38126?focusedCommentId=270359&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-270359]

Could you explain further what you are seeing? Specifically, I'm not clear on the steps you took so that you could {quote}see the credentials properly in the system configuration but not on job configuration{quote}.

mark.earl.waite@gmail.com (JIRA)

unread,

Nov 18, 2016, 8:06:04 AM11/18/16

to jenkinsc...@googlegroups.com

Mark Waite updated an issue

Jenkins /

Change By:	Mark Waite
Comment:

[~kralleman] and [~paul_symphony] I am unable to duplicate the problem you're seeing. Can you provide more details about the conditions when you see the problem. Steps I checked:

h3. Global Pipeline Credentials (as fixed by Jesse Glick's [PR437|https://github.com/jenkinsci/git-plugin/pull/437])

# Add a global pipeline library named "globalPipelineLibraryMarkEWaiteprivate"
# Configure the global pipeline library "globalPipelineLibraryMarkEWaiteprivate" to use git as "Legacy SCM"
# Click the credentials drop down before entering any URL, confirm all credentials appear
# Enter a private URL in the "Repository URL" field
# Click the credentials drop down after entering the URL, confirm only credentials for that private repository appear
# Observe that intentionally invalid credentials for that private repository can be selected but show red text that they don't authorize access to that private repository
# Observe that valid credentials for that private repository do not show red text when they are selected

h3. Job Credentials

# Define a new job "JENKINS-38126-credentials-dropdown-empty"
# Use Git as the SCM for that job
# Confirm that the credentials dropdown for the job shows all credentials prior to entering any repository URL
# Enter a repository URL
# Confirm that the credentials dropdown for the job shows only credentials matching that repository URL (I checked with a private github.com URL and a private bitbucket.org URL)
# Save the job
# Confirm that the job runs successfully (clones from the private repository, etc.)

h3. Fresh Install and Job Credentials

# Refer to my [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-38126?focusedCommentId=270359&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-270359]

Could you explain further what you are seeing? Specifically, I'm not clear on the steps you took so that you could {quote}see the credentials properly in the system configuration but not on job configuration{quote}.

k.hansson.aspman@gmail.com (JIRA)

unread,

Nov 23, 2016, 6:32:02 AM11/23/16

to jenkinsc...@googlegroups.com

Kristofer Hansson Aspman commented on

It seems as if I tried to use the wrong credentials. I added credentials as part of the configuration of the GitHub Pull Request-builder plugin (according to these instructions https://github.com/jenkinsci/ghprb-plugin). I tried to use those together with the regular git-scm-configuration for a job. When I added a separate (user/password) credential for that part of the configuration (i.e. the regular git-scm-configuration) it worked.

I am still not sure if I should've been able to choose the ones configured for the GitHub PR-builder plugin, but it might very well be the case that I am lacking some understanding of how those are supposed to work. Sorry for the confusion.

mark.earl.waite@gmail.com (JIRA)

unread,

Nov 26, 2016, 11:36:04 AM11/26/16

to jenkinsc...@googlegroups.com

Mark Waite edited a comment on

[~kralleman] and [~paul_symphony] I am unable to duplicate the problem you're seeing. Can you provide more details about the conditions when you see the problem. Steps I checked:

h3. Global Pipeline Credentials (as fixed by Jesse Glick's [PR437|https://github.com/jenkinsci/git-plugin/pull/437] for JENKINS-38048)

# Add a global pipeline library named "globalPipelineLibraryMarkEWaiteprivate"
# Configure the global pipeline library "globalPipelineLibraryMarkEWaiteprivate" to use git as "Legacy SCM"
# Click the credentials drop down before entering any URL, confirm all credentials appear
# Enter a private URL in the "Repository URL" field
# Click the credentials drop down after entering the URL, confirm only credentials for that private repository appear
# Observe that intentionally invalid credentials for that private repository can be selected but show red text that they don't authorize access to that private repository
# Observe that valid credentials for that private repository do not show red text when they are selected

h3. Job Credentials

# Define a new job "JENKINS-38126-credentials-dropdown-empty"
# Use Git as the SCM for that job
# Confirm that the credentials dropdown for the job shows all credentials prior to entering any repository URL
# Enter a repository URL
# Confirm that the credentials dropdown for the job shows only credentials matching that repository URL (I checked with a private github.com URL and a private bitbucket.org URL)
# Save the job
# Confirm that the job runs successfully (clones from the private repository, etc.)

h3. Fresh Install and Job Credentials

# Refer to my [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-38126?focusedCommentId=270359&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-270359]

Could you explain further what you are seeing? Specifically, I'm not clear on the steps you took so that you could {quote}see the credentials properly in the system configuration but not on job configuration{quote}.

[~paul_symphony], as far as I can tell, you're reporting a different problem (can't see credentials when defining a global pipeline library rather than the bug that [~lifeofguenter] reported that he can't see credentials in an individual job). The "can't see credentials when defining a global pipeline library" was reported as JENKINS-38048 and is resolved in git plugin 3.0.1

paul@symphony.com (JIRA)

unread,

Nov 28, 2016, 9:56:02 AM11/28/16

to jenkinsc...@googlegroups.com

Paul Pollack commented on

Mark Waite that sounds right, thanks.

gunter@grodotzki.co.za (JIRA)

unread,

Dec 17, 2016, 12:50:02 AM12/17/16

to jenkinsc...@googlegroups.com

Gunter Grodotzki commented on

I upgraded:

jenkins: 2.19.4
git-plugin: 3.0.1

Problem still remaining, similar to what Kristofer Hansson Aspman is describing. Unfortunately I have yet again to downgrade the git-plugin manually to 2.5.3.

Obviously a error is happening, can someone in this thread be so kind to at least help with debugging? E.g. there surely must be somewhere a error log happening?

mark.earl.waite@gmail.com (JIRA)

unread,

Dec 17, 2016, 8:28:02 AM12/17/16

to jenkinsc...@googlegroups.com

Mark Waite commented on

Gunter Grodotzki, you say you're seeing something similar to what Kristofer Hansson Aspman is seeing, yet he says, "it seems as if I tried to use the wrong credentials". Please review the credentials you're expecting to see in that drop-down menu, and confirm that they are either private key credentials (for ssh and scp git URL's) or username / password credentials (for https URL's). Those are the only two credential types supported by the git plugin.

If there is an error log, you should be able to find that error log from the Jenkins system level logs. If you find that error log, please post it to the bug report, since it will provide additional hints.

The single most effective thing you can do is provide a way to duplicate the problem. Step by step procedures are the best, since then someone else can perform those same steps and see the problem. The empty global credential dropdown includes the steps I use to see the problem. As far as I understand, that's not the problem you're having. Please provide detailed steps which show the problem on a freshly installed system.

gunter@grodotzki.co.za (JIRA)

unread,

Dec 17, 2016, 2:57:03 PM12/17/16

to jenkinsc...@googlegroups.com

Gunter Grodotzki commented on

I can not reproduce it with another installation, thats what makes me think it is an incapability issue with the xml config files? Since everything works with an older version of the git-plugin there must surely be a change that is regressing? E.g. I can 100% proof that this is an issue with git-plugin > 2.5.3, just can not proof any reproducing steps

E.g. simple reproducing:

upgrade to anything > 2.5.3
go to any job
"creds with id xxx-xxx-xxx-xxx not found"

Fix:

downgrade back to 2.5.3
go to any job
any ssh + private key credentials are selectable

gunter@grodotzki.co.za (JIRA)

unread,

Dec 17, 2016, 2:57:04 PM12/17/16

to jenkinsc...@googlegroups.com

Gunter Grodotzki edited a comment on

I can not reproduce it with another installation, thats what makes me think it is an incapability issue with the xml config files? Since everything works with an older version of the git-plugin there must surely be a change that is regressing? E.g. I can 100% proof that this is an issue with git-plugin > 2.5.3 as it will *fail reliably* , just can not proof any reproducing steps :)

E.g. simple reproducing:

* upgrade to anything > 2.5.3
* go to any job
* "creds with id xxx-xxx-xxx-xxx not found"

Fix:

* downgrade back to 2.5.3
* go to any job
* any ssh + private key credentials are selectable

matt.wilson@entrust.com (JIRA)

unread,

Jan 18, 2017, 3:23:01 PM1/18/17

to jenkinsc...@googlegroups.com

Matt Wilson commented on

(sorry, this gets long winded )
I'm seeing the same behavior on my system right now. I had this issue some time ago, but never had the time to investigate it very thoroughly.
My current "live" system is
Jenkins 1.651.1
Git Plugin 2.4.4
Credentials Plugin 2.1.4
This setup works. A few months ago I upgraded all my plugins. This upgraded the git plugin to 3.0.0, and I started seeing this behavior of not being able to select any credentials. The only thing that got things working again was to downgrade my Git plugin to 2.4.4.

Fast forward to today.
I'm currently testing a procedure for migrating my Jenkins environment to a new server.
I moved all my content over.
Fire up jenkins (same version 1.651.1) every thing works fine.
I try upgrading my server to 2.32.1. Jenkins comes up, everything looks fine.
I try updating all my plugins to the latest... Git Plugin no longer lets me select any credentials. If I add new credentials, I don't see them. I see them in the credential manager, but not in the Git SCM section
So that puts me here:
Git Plugin 3.0.1
Credentials Plugin 2.1.10

So at this point I try downgrading to version 2.4.4 as my system gives me that option. After downgrade, git credentials work. That was expected. Anyway, now I think that maybe I should try uninstalling the git plugin and reinstalling (This isn't my live box, so I'm willing to screw around with it.). I had to uninstall a bunch of plugins that depend on the Git Plugin. So I get it off, restart, then reinstall the Git Plugin. Same result. I can't see any credentials. Btw, I can't see any credentials on upgraded jobs, or brand new jobs.

so that is where I stand at this point. Unfortunately I can share my image with anyone. I am willing to try stuff out if anyone has any ideas...

gunter@grodotzki.co.za (JIRA)

unread,

Feb 3, 2017, 1:36:02 AM2/3/17

to jenkinsc...@googlegroups.com

Gunter Grodotzki commented on

I have been doing some changes on the system in the meanwhile, unfortunately same problem:

completely re-installed the server from scratch (minimalised the master) on Debian 8, latest Java, latest Jenkins LTS
only kept the /var/lib/jenkins folder
removed the bitbucket plugin which was causing a lot of problems with jenkins cron runner (e.g. crons would intermittently just fail)

Still, once updating git, the drop down mal-functions. Is there any way for me to produce a log so it can help here? Obviously there must be an error happening? Or is this the desired behaviour?

gunter@grodotzki.co.za (JIRA)

unread,

Feb 3, 2017, 1:38:02 AM2/3/17

to jenkinsc...@googlegroups.com

Gunter Grodotzki updated an issue

Jenkins /

Change By:	Gunter Grodotzki

Since recently (might be through the 2.7.3 to 2.7.4 upgrade) I am unable to select any credentials with the git settings directly in the job configuration.

Even if I add credentials, it does not show in the list.

Any advices?

{code}
$ java -version
java version "1.8.0_102"
Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)
{code}

{code}
$ git --version
git version 1.9.1
{code}

{code}
Ubuntu 14.04 LTS latest apt update && apt upgrade
{code}

Meanwhile switched the system, but same problem:

{code}
$ java -version
java version "1.8.0_112"
Java(TM) SE Runtime Environment (build 1.8.0_112-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)
{code}

{code}
$ git --version
git version 2.1.4
{code}

{code}
Debian 8 latest apt update && apt upgrade
{code}

chief7@gmail.com (JIRA)

unread,

Feb 15, 2017, 4:26:01 PM2/15/17

to jenkinsc...@googlegroups.com

Robb Schiefer commented on

Only in my first day of Jenkins use but I found I had to create my secret text credential in the global domain to get it to show as an option in the GitHub Server configuration on the Jenkins Configuration page .

matt.wilson@entrust.com (JIRA)

unread,

Feb 17, 2017, 2:42:03 PM2/17/17

to jenkinsc...@googlegroups.com

Matt Wilson commented on

Not sure if this helps anyone, but I've managed to at least get mine to list a stack trace. My expectation is that this behavior is being caused by a 3rd plugin.
Here is the stack trace I'm seeing on my job page.

javax.servlet.ServletException: java.lang.NoSuchMethodError: com.cloudbees.plugins.credentials.CredentialsProvider.listCredentials(Ljava/lang/Class;Lhudson/model/Item;Lorg/acegisecurity/Authentication;Ljava/util/List;Lcom/cloudbees/plugins/credentials/CredentialsMatcher;)Lhudson/util/ListBoxModel;
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:614)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:958)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:452)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1087)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoSuchMethodError: com.cloudbees.plugins.credentials.CredentialsProvider.listCredentials(Ljava/lang/Class;Lhudson/model/Item;Lorg/acegisecurity/Authentication;Ljava/util/List;Lcom/cloudbees/plugins/credentials/CredentialsMatcher;)Lhudson/util/ListBoxModel;
at hudson.plugins.git.UserRemoteConfig$DescriptorImpl.doCheckCredentialsId(UserRemoteConfig.java:140)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
... 70 more

matt.wilson@entrust.com (JIRA)

unread,

Feb 17, 2017, 2:54:02 PM2/17/17

to jenkinsc...@googlegroups.com

Matt Wilson updated an issue

Jenkins /

Comment:
Change By:	Matt Wilson

matt.wilson@entrust.com (JIRA)

unread,

Feb 23, 2017, 10:54:05 AM2/23/17

to jenkinsc...@googlegroups.com

Matt Wilson commented on

Okay, I've done some fairly exhaustive testing (pretty much blunt force style) and I've found what is causing MY Jenkins installation problems. Keep in mind this may not be your cause, but it directly causes the unwanted behavior. I setup a secondary environment, installed all my plugins, copied over my jenkins configuration files (site and plugins) then started removing plugin configurations one by one (restarting the jenkins process as I went along).

My problems seem to be stemming from the "Authorize Project Plugin"
https://wiki.jenkins-ci.org/display/JENKINS/Authorize+Project+plugin

I have a this plugin installed. Under "Configure Global Security" I have set a "Project default Build Authorization" strategy set to "Run as Specific User". The other options here are:
"Run as User who Triggered Build"
"Run as anonymous"
"Run as SYSTEM"

If this value is set to "Run as Specific User", or "Run as anonymous" I lose my ability in my job configuration screen to select any credentials for get to use.
This also seems to apply if I use "Per-project configuable Build Authorization" instead of "Project default Build Authorization".

I'm not sure where the issue lies here. Is it the Git Plugin, or the Authorize Project Plugin?

gunter@grodotzki.co.za (JIRA)

unread,

Mar 4, 2017, 4:39:03 AM3/4/17

to jenkinsc...@googlegroups.com

Gunter Grodotzki commented on

Matt Wilson, I owe you a beer! This was exactly the reason for our problems as well.

I switched "Project default Build Authorization" to "Run as User who Triggered Build", which fixes the problem of the git-creds dropdown, but for that I am now getting the following warnings on downstream builds:

09:24:01 Warning: this build has no associated authentication, so build permissions may be lacking, and downstream projects which cannot even be seen by an anonymous user will be silently skipped

Downstream jobs still seem to be triggered, but they are not anymore directly linked within the console-output.

To me the security setup of Jenkins does not fully make sense:

why can downstream jobs just not assume the user that triggered the upstream job?
why can there not be a "special" user that can be used for scm-polling/trigger/timer? Some documentations suggest SYSTEM is anonymous?

matt.wilson@entrust.com (JIRA)

unread,

Mar 6, 2017, 9:38:01 AM3/6/17

to jenkinsc...@googlegroups.com

Matt Wilson commented on

Gunter Grodotzki I'll take it!

I'm also experimenting with "Run as User Who Triggered Build". Its a compromise for sure. Running everything as one user solves a lot of little issues. I'm not sure if this fault lies with the git plugin, the credentials plugin, or the authorization plugin. I do know it would be nice if this worked...

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

matthias.flock@gmail.com (JIRA)

unread,

Jul 24, 2019, 2:20:03 AM7/24/19

to jenkinsc...@googlegroups.com

Matthias Flock commented on