[JIRA] (JENKINS-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title
Christopher Sullivan updated an issue
Jenkins / JENKINS-32402
Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs
Change By:
Christopher Sullivan
Comment:
I worked around this issue by using the [Authorize Project plugin|https://wiki.jenkins.io/display/JENKINS/Authorize+Project+plugin]. Instead of passing the credentials from the upstream job, I set the {{defaultValue}} of the parameter instead to globally scoped credentials.For build "Authorization" (enabled by Authorize Project), I set the job to run as a user with access to the global credentials (I would have used credentials scoped to the user only, but you can't use these as default values). When selecting "Build with Parameters" as any other user, only the user scoped credentials are available.Other users can still pass parameters to the job and successfully run it if they have the correct credentials.- If they try to run the job without specifying their own credentials, they can not access the default credentials and the job fails as desired.- (still working on restricting access to the credentials)When initiated by timer, it uses the default globally scoped credentials and successfully runs.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title
Christopher Sullivan edited a comment on JENKINS-32402
Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs
I worked around this issue by using the [Authorize Project plugin|https://wiki.jenkins.io/display/JENKINS/Authorize+Project+plugin]. Instead of passing the credentials from the upstream job, I set the {{defaultValue}} of the parameter instead to globally scoped credentials.For build "Authorization" (enabled by Authorize Project), I set the job to run as a user with access to the global credentials (I would have used credentials scoped to the user only, but you can't use these as default values). When selecting "Build with Parameters" as any other user, only the user scoped credentials are available.Other users can still pass parameters to the job and successfully run it if they have the correct credentials. - If they try to run the job without specifying their own credentials, they can not access the default credentials and the job fails as desired. - (still working on restricting access to the credentials) When initiated by timer, it uses the default globally scoped credentials and successfully runs.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title Christopher Sullivan commented on JENKINS-32402 Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs I worked around this issue by using the Authorize Project plugin. Instead of passing the credentials from the upstream job, I set the defaultValue of the parameter instead to globally scoped credentials. For build "Authorization" (enabled by Authorize Project), I set the job to run as a user with access to the global credentials (I would have used credentials scoped to the user only, but you can't use these as default values). When selecting "Build with Parameters" as any other user, only the user scoped credentials are available. Other users can still pass parameters to the job and successfully run it if they have the correct credentials. If they try to run the job without specifying their own credentials, they can not access the default credentials and the job fails as desired. When initiated by timer, it uses the default globally scoped credentials and successfully runs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title Maksym Kit commented on JENKINS-32402 Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs I observe the same behavior. I have a Job A, which triggers Job B and passes an credentials ID using Jenkins Parameterized Trigger Plugin Predefined parameters. Job B project is parameterized and has Credentials Parameter specified. Job B also has "Use secret text(s) or file(s)" enabled (provided with Credentials Binding Plugin) and a corresponding binding specified. When I start Job A manually Job B will start correctly and have credentials resolved correctly, however when Job A is being triggered by GitHub push Job B will fail to resolve credentials. Sounds like a user error. Credentials parameters could not be used across jobs like this. Why? 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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title Jesse Glick commented on JENKINS-32402 Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs Sounds like a user error. Credentials parameters could not be used across jobs like this. You would need to have the upstream extract the secret and then pass it downstream via a password parameter, I suppose. 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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title Guillaume Coré commented on JENKINS-32402 Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs > For you information, I created new credentials and let Jenkins generating the ID instead of setting it and it worked. Mathieu Beausoleil i tried, creating a new credentials with generated ID does not fix the issue for me 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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-32402 Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs Change By: Jesse Glick Assignee: Jesse Glick 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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title bryan patton edited a comment on JENKINS-32402 Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs I am having the same issue and to compound it when rebuilding the project task it will work correctly. It appears to be a difference between Jenkins identifying the credentials and binding them and or not. 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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title bryan patton commented on JENKINS-32402 Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs I am having the same issue and to compound it when rebuilding the project it will work correctly. It appears to be a difference between Jenkins identifying the credentials and binding them and not. 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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title
Alexandre Aubert edited a comment on JENKINS-32402
Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs
Hi,I'm facing the same issue, here is the description : I have a multibranch pipeline that triggered another job with parameters, here is the trigger block : ~ build job: 'Archis/front-s3-deployer',parameters: [string(name: 'SourcePackagePath', value: "Internal/DataViz/Vega/${env.BRANCH_NAME}/Binary/${env.BUILD_NUMBER}/"),string(name: 'SourcePackageName', value: 'vega.zip'),string(name: 'DestinationBucket', value: 'datavizclouddev.net'),string(name: 'DestinationPath', value: 'vega/'),[$class: 'CredentialsParameterValue', description: 'Credentials used to write on the destination bucket', name: 'StoredAccessKeyName', value: 'aws-dataviz']] ~ If i launch this job manually, parameters are well passed to second job and second job builds ok : ^ Started by upstream project "DataViz/VegaWebApp/Vega-Deploy/dev" build number 159originally caused by: *Started by user Alexandre*[EnvInject] - Loading node environment variables.Building remotely on Archis - awsbld001 (Archis BDXBLD013 -) in workspace /home/admin/jenkins/workspace/Archis/front-s3-deployer[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] Done[front-s3-deployer] $ /bin/sh -xe /tmp/hudson5564189863560131079.sh... ^ If this job is trigger automatically, i can see that parameters are well passed to second job (by checking the 'parameters' page of the triggered build : all values are well populated - exactly as for the manually triggered run) but i got an error message when second job's build starts : ^ Started by upstream project "DataViz/VegaWebApp/Vega-Deploy/dev" build number 160originally caused by: *Branch indexing*[EnvInject] - Loading node environment variables.Building remotely on Archis - awsbld001 (Archis BDXBLD013 -) in workspace /home/admin/jenkins/workspace/Archis/front-s3-deployer[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] DoneFATAL: ${StoredAccessKeyName}org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: ${StoredAccessKeyName} at org.jenkinsci.plugins.credentialsbinding.MultiBinding.getCredentials(MultiBinding.java:131) at com.cloudbees.jenkins.plugins.awscredentials.AmazonWebServicesCredentialsBinding.bind(AmazonWebServicesCredentialsBinding.java:93) at org.jenkinsci.plugins.credentialsbinding.impl.SecretBuildWrapper.setUp(SecretBuildWrapper.java:96) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1729) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Notifying upstream projects of job completion... ^ Environment : Jenkins 2.41Credential-bindings 1.10Credentials Plugin 2.1.10CloudBees Amazon Web Services Credentials Plugin 1.17
[JIRA] (JENKINS-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title
Alexandre Aubert commented on JENKINS-32402
Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs
Hi, I'm facing the same issue, here is the description : I have a multibranch pipeline that triggered another job with parameters, here is the trigger block : ~ build job: 'Archis/front-s3-deployer', parameters: [ string(name: 'SourcePackagePath', value: "Internal/DataViz/Vega/$ {env.BRANCH_NAME} /Binary/$ {env.BUILD_NUMBER} /"), string(name: 'SourcePackageName', value: 'vega.zip'), string(name: 'DestinationBucket', value: 'datavizclouddev.net'), string(name: 'DestinationPath', value: 'vega/'), [$class: 'CredentialsParameterValue', description: 'Credentials used to write on the destination bucket', name: 'StoredAccessKeyName', value: 'aws-dataviz'] ]~ If i launch this job manually, parameters are well passed to second job and second job builds ok : ^Started by upstream project "DataViz/VegaWebApp/Vega-Deploy/dev" build number 159 originally caused by: Started by user Alexandre [EnvInject] - Loading node environment variables. Building remotely on Archis - awsbld001 (Archis BDXBLD013 -) in workspace /home/admin/jenkins/workspace/Archis/front-s3-deployer [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Done [front-s3-deployer] $ /bin/sh -xe /tmp/hudson5564189863560131079.sh ...^ If this job is trigger automatically, i can see that parameters are well passed to second job (by checking the 'parameters' page of the triggered build : all values are well populated - exactly as for the manually triggered run) but i got an error message when second job's build starts : ^Started by upstream project "DataViz/VegaWebApp/Vega-Deploy/dev" build number 160 originally caused by: Branch indexing [EnvInject] - Loading node environment variables. Building remotely on Archis - awsbld001 (Archis BDXBLD013 -) in workspace /home/admin/jenkins/workspace/Archis/front-s3-deployer [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Done FATAL: $ {StoredAccessKeyName} org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: ${StoredAccessKeyName} at org.jenkinsci.plugins.credentialsbinding.MultiBinding.getCredentials(MultiBinding.java:131) at com.cloudbees.jenkins.plugins.awscredentials.AmazonWebServicesCredentialsBinding.bind(AmazonWebServicesCredentialsBinding.java:93) at org.jenkinsci.plugins.credentialsbinding.impl.SecretBuildWrapper.setUp(SecretBuildWrapper.java:96) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1729) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Notifying upstream projects of job completion ...^ Environment : Jenkins 2.41 Credential-bindings 1.10 Credentials Plugin 2.1.10 CloudBees Amazon Web Services Credentials Plugin 1.17
[JIRA] (JENKINS-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title André Bierlein commented on JENKINS-32402 Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs I am currently running into what I believe to be the same issue as Martin S.. I have a job that is triggered by git push, which has a few promotions for different environments. The promotions all trigger the same deployment job with different values for the credential parameter. When I run the promotion I get the CredentialNotFoundException, while triggering the deployment manually works perfectly fine. When comparing the two builds (manual vs promoted) they look absolutely identical, both showing the credentials that I provided as well as the respective environment variable. It's not obvious to me how exactly these invocations differ from each other, so I don't know if this is a bug or a configuration mistake on my side. 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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title Jesse Glick commented on JENKINS-32402 Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs Possibly a duplicate of JENKINS-35490? 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.
