Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-27398

Pipeline-as-Code CredentialsProvider for a job

    XMLWordPrintable

Details

    Description

      There should be an analogue of FolderCredentialsProvider limited to a single Job, allowing credentials to be set on the narrowest possible scope.

      Not Workflow specific, but arguably more important for flows since they are likely to replace a whole set of freestyle projects that might otherwise have been segregated into a distinct folder.

      Attachments

        Issue Links

          is related to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-27386 Access credentials value from workflow Groovy script

          • Major - Major loss of function.
          • Resolved
          relates to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-36007 Way to mask arbitrary Secret (was: Password is clear on log with input parameter)

          • Critical - Crashes, loss of data, severe memory leak.
          • Open

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-43633 Scope credentials to branch being built

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open
          links to

          Web Link CloudBees Internal CD-242

          Activity

            Ascending order - Click to sort in descending order
            View 7 older comments
            abayer Andrew Bayer added a comment -

            That might work, but I wouldn't want to make any assumptions or implementations until after JENKINS-42753 has landed, given how drastically it changes parsing.

            abayer Andrew Bayer added a comment - That might work, but I wouldn't want to make any assumptions or implementations until after JENKINS-42753 has landed, given how drastically it changes parsing.
            jglick Jesse Glick added a comment -

            Sure, I just meant to draw a sketch of what it might look like from a user perspective, not a concrete syntax.

            jglick Jesse Glick added a comment - Sure, I just meant to draw a sketch of what it might look like from a user perspective, not a concrete syntax.
            rtyler R. Tyler Croy added a comment -

            I would love for this work to exist, so I could ditch my experimental inline-pipeline-secrets work.

            The key thing from a user perspective (IMHO), is that somebody who is authorized to modify the Jenkinsfile should be able to easily create the ciphertext (or Credential, I don't care what it is), which could be written into the Jenkinsfile.

            This would be conceptually similar to how Travis CI allows creating encrypted tokens per-job.

            rtyler R. Tyler Croy added a comment - I would love for this work to exist, so I could ditch my experimental inline-pipeline-secrets work . The key thing from a user perspective (IMHO), is that somebody who is authorized to modify the Jenkinsfile should be able to easily create the ciphertext (or Credential, I don't care what it is), which could be written into the Jenkinsfile . This would be conceptually similar to how Travis CI allows creating encrypted tokens per-job.
            jglick Jesse Glick added a comment -

            rtyler yes that is the idea exactly.

            jglick Jesse Glick added a comment - rtyler yes that is the idea exactly.
            rtyler R. Tyler Croy added a comment -

            Then yes please, i'll take eleventy of those immediately thanks.

            rtyler R. Tyler Croy added a comment - Then yes please, i'll take eleventy of those immediately thanks.

            People

              jglick Jesse Glick
              jglick Jesse Glick
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated: