From b89610fe09a543fd75bc8902c894eae0557ea3c7 Mon Sep 17 00:00:00 2001 From: Sebastian Schuberth Date: Tue, 21 Nov 2023 14:25:09 +0100 Subject: [PATCH] docs(jenkins): Clarify that the credentials type should be for HTTP Later steps use the `usernamePassword()` pipeline function [1] which assumes credentials to be composed of a username and password for HTTP authentication. Clarify this to avoid users specifying e.g. SSH credentials which would result in ERROR: Credentials 'jenkins-ssh' is of type 'SSH Username with private key' where 'com.cloudbees.plugins.credentials.common.StandardUsername PasswordCredentials' was expected [1]: https://www.jenkins.io/doc/pipeline/steps/credentials-binding/ Signed-off-by: Sebastian Schuberth --- integrations/jenkins/Jenkinsfile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/integrations/jenkins/Jenkinsfile b/integrations/jenkins/Jenkinsfile index f98e7af412856..c4a1003186276 100644 --- a/integrations/jenkins/Jenkinsfile +++ b/integrations/jenkins/Jenkinsfile @@ -62,7 +62,7 @@ pipeline { credentials( name: 'PROJECT_VCS_CREDENTIALS', - description: 'Optional Jenkins credentials to use for the VCS checkout.', + description: 'Optional HTTP credentials to use for the VCS checkout.', defaultValue: '' ) @@ -84,7 +84,7 @@ pipeline { credentials( name: 'ORT_CONFIG_VCS_CREDENTIALS', - description: 'Optional Jenkins credentials to use for the VCS checkout.', + description: 'Optional HTTP credentials to use for the VCS checkout.', defaultValue: '' )