[JIRA] (JENKINS-23977) Promoted-builds does not allow build secrets

[monilpatel536@gmail.com (JIRA)]

Monil Patel updated an issue

Jenkins / JENKINS-23977 Promoted-builds does not allow build secrets Change By: Monil Patel Priority: Major Critical Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated JENKINS-23977

Jenkins / JENKINS-23977 Promoted-builds does not allow build secrets

Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated JENKINS-23977

It was fixed in Promoted Builds 3.3

Jenkins / JENKINS-23977 Promoted-builds does not allow build secrets

Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed Released As: Promoted Builds 3.3

Add Comment

[andys@andyshinn.as (JIRA)]

Andy Shinn commented on JENKINS-23977

Re: Promoted-builds does not allow build secrets I can't seem to get this working (or maybe am not understanding it correctly). I have a promotion which sets a predefined parameter of credentialssh=analytics-jenkins-deployer-staging. In my triggered downstream job I have a credential parameter named credentialssh. When the downstream job is triggered by the promotion I get a failure with error: ERROR: Could not find credentials entry with ID '${credentialssh}' But when I run it manually it works fine. Ideas?

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[catsup@gmail.com (JIRA)]

Jason H commented on JENKINS-23977

Re: Promoted-builds does not allow build secrets

I also hit this when this is kicked off from an automatic upstream job.  When I kick it off from the same upstream job it loads without failure.  Anyone find a workaround to this?

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[catsup@gmail.com (JIRA)]

Jason H edited a comment on JENKINS-23977

Re: Promoted-builds does not allow build secrets

I also hit this when this is kicked off from an automatic upstream job.  When I kick it off manually from the same upstream job it loads without failure.  Anyone find a workaround to this?

Add Comment