| This is how my job's config.xml starts
<?xml version='1.1' encoding='UTF-8'?>
<org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject plugin="workflow-m...@2.21">
<actions/>
<description>test</description>
<properties>
<io.jenkins.blueocean.rest.impl.pipeline.credential.BlueOceanCredentialsProvider_-FolderPropertyImpl plugin="blueocean-pip...@1.14.0">
<domain plugin="crede...@2.1.19">
<name>blueocean-folder-credential-domain</name>
<description>Blue Ocean Folder Credentials domain</description>
<specifications/>
</domain>
<user>testuser</user>
<id>github-enterprise:bd08318e10264d38792523a9e76b6f818f8ec73616f7b13b99692ed940ce642c</id>
</io.jenkins.blueocean.rest.impl.pipeline.credential.BlueOceanCredentialsProvider_-FolderPropertyImpl>
<org.jenkinsci.plugins.pipeline.modeldefinition.config.FolderConfig plugin="pipeline-mod...@1.3.8">
<dockerLabel></dockerLabel>
<registry plugin="docker-...@1.14"/>
</org.jenkinsci.plugins.pipeline.modeldefinition.config.FolderConfig>
</properties>
And I wonder if the BlueOceanCredentialProvider which references the testuser's credential can be changed to use the global credential instead. I already have a jenkins level github enterprise access token credential, so i would like to just use that. That token btw was issued to a service account which is also added on the GitHub Enterprise side with a nice Jenkins icon, so it looks much better than the pipeline creator's photo next to a Pull request check. I've just changed the testuser to jenkins user then updated the user level credential as well and it works, but it's hacky and too involved. |
