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

API call using credentials stored inside jenkins.

      Hello, good afternoon, 

      I have made a pipeline that downloads an image, converts it and uploads it to a converted repository. 

      If I run the pipeline in jenkins filling the parameters as I have defined, it runs correctly from start to finish. 

      The thing is that I want to be able to trigger that pipeline from outside jenkins. To do this I have been trying to make an API call, passing the parameters following the structure that is in the documentation, but there are two parameters that I can not pass, since they are credentials that I entered my user inside jenkins to use them, making use of withCredentials to use the credentials to download the snapshot and then to access the repository where I upload it. 

      Is it possible to pass by curl the id of the credentials to run the pipeline correctly? With String parameters I have no problem, but with credential parameters I am having problems and I haven't seen any example with it. 

          [JENKINS-69051] API call using credentials stored inside jenkins.

          Mark Waite added a comment -

          Please don't use the Jenkins issue tracker to ask Pipeline implementation questions. Many more people read the Jenkins community forum, the Jenkins gitter chat channel, and the Jenkins user mailing list.

          We want to reserve the issue tracker for bugs and for enhancements, not for question and answer.

          Mark Waite added a comment - Please don't use the Jenkins issue tracker to ask Pipeline implementation questions. Many more people read the Jenkins community forum , the Jenkins gitter chat channel , and the Jenkins user mailing list . We want to reserve the issue tracker for bugs and for enhancements, not for question and answer.

            Unassigned Unassigned
            nahook Ignacio Sayago
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: