-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.46.2
Trigger Plug-In 2.25.0
With the gerrit trigger plugin, you must specify a ssh private key that exists on disk. When working in an enterprise Jenkins environment, this is a bit trickier, as we now need to inject the credentials into our Managed Master docker image. We already have the ssh credentials for our build account managed by the credentials manager, and it's a bit redundant to have to specify them again in the trigger plug-in, possibly in a different manner. It would make more sense for the trigger plugin to just use credentials that already exist.