On Tuesday 27 September 2016, wrote:
> I ran across this thread while trying to solve a similar problem writing
> Pipelines with Jenkins 2. I installed the Authorize Project plugin, set my
> Pipeline job to run as user that triggered, and tried to use a Credential
> Parameter to get the ID and p
I ran across this thread while trying to solve a similar problem writing
Pipelines with Jenkins 2. I installed the Authorize Project plugin, set my
Pipeline job to run as user that triggered, and tried to use a Credential
Parameter to get the ID and pass it to my Pipeline from SCM. The paramet
It depends on how the plugin has been written. If it is written correctly,
then it should allow the user to select their own credentials if they have
the appropriate permissions (I cannot recall, but you may have to enable a
permission by system property... Or it could be a bug in the gitlab plugin
Step 1: Install the Authorize Project plugin
Step 2: configure the jobs to run as the user
Step 3: have the user put their credentials in their per-user credentials
store
Step 4: don't put credentials in the Jenkins System credentials store
Step 5: Sit back, light your pipe and enjoy the satisfacti
