Credential types and storage in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Jenkins Credential Types

Which Jenkins credential type is best suited to store a username and password pair securely?

A Username with password

B Certificate

C SSH Username with private key

D Secret text

💡 Hint

Think about which type explicitly stores both username and password together.

The 'Username with password' credential type is designed to securely store a username and its associated password. Other types store different secrets like text, SSH keys, or certificates.

💻 Command Output

intermediate

Jenkins CLI Credential Listing Output

What is the output of the following Jenkins CLI command when listing credentials in a folder named 'projectA'?

java -jar jenkins-cli.jar -s http://jenkins.example.com/ list-credentials projectA

A Error: No credentials found in folder 'projectA'

B

[id: 'cred1', type: 'Username with password', description: 'GitHub creds']
[id: 'cred2', type: 'Secret text', description: 'API token']

C SyntaxError: Invalid command format

D [id: 'cred1', type: 'SSH Username with private key', description: 'Deploy key']

💡 Hint

Assume the folder 'projectA' contains two credentials: one username/password and one secret text.

The command lists all credentials in the specified folder. Since 'projectA' has two credentials, the output shows both with their ids, types, and descriptions.

❓ Configuration

advanced

Jenkinsfile Using Credentials Binding

Which Jenkinsfile snippet correctly uses the 'usernamePassword' credentials binding to inject username and password environment variables?

A

pipeline {
  agent any
  environment {
    CREDS = credentials('my-cred-id')
  }
  stages {
    stage('Build') {
      steps {
        echo "User: $CREDS_USR"
        echo "Pass: $CREDS_PSW"
      }
    }
  }
}

B

pipeline {
  agent any
  environment {
    USER = credentials('my-cred-id')
  }
  stages {
    stage('Build') {
      steps {
        echo "User: $USER"
      }
    }
  }
}

C

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        withCredentials([string(credentialsId: 'my-cred-id', variable: 'TOKEN')]) {
          echo "Token: $TOKEN"
        }
      }
    }
  }
}

D

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        withCredentials([usernamePassword(credentialsId: 'my-cred-id', usernameVariable: 'USER', passwordVariable: 'PASS')]) {
          echo "User: $USER"
          echo "Pass: $PASS"
        }
      }
    }
  }
}

💡 Hint

Look for the correct use of withCredentials and variable names for username and password.

Option D correctly uses withCredentials with usernamePassword binding and defines separate variables for username and password. Other options misuse environment or credential types.

❓ Troubleshoot

advanced

Jenkins Credential Access Error

A Jenkins pipeline fails with the error: java.lang.IllegalArgumentException: No credentials found with id 'deploy-key'. What is the most likely cause?

A The pipeline syntax for accessing credentials is incorrect and causes this error.

B The Jenkins agent does not have internet access to fetch the credential.

C The credential with id 'deploy-key' does not exist or is not accessible in the current folder or global scope.

D The Jenkins master is offline and cannot provide credentials.

💡 Hint

Consider where credentials are stored and their scope in Jenkins.

This error usually means Jenkins cannot find the credential with the given id in the current folder or global credentials store. It is a scope or existence issue, not network or syntax.

✅ Best Practice

expert

Secure Storage of API Tokens in Jenkins

Which is the most secure and recommended way to store and use API tokens in Jenkins pipelines?

A Store the API token as a 'Secret text' credential and use <code>withCredentials</code> to inject it as an environment variable during the pipeline run.

B Hardcode the API token directly in the Jenkinsfile for easy access.

C Store the API token in a plain text file on the Jenkins master and read it during the build.

D Use the 'Username with password' credential type but leave the username empty.

💡 Hint

Think about avoiding exposure of secrets and following Jenkins best practices.

Storing API tokens as 'Secret text' credentials and injecting them securely during pipeline execution prevents exposure in code or logs. Hardcoding or storing in files is insecure. Using username/password with empty username is not appropriate.