External artifact repositories (Nexus, Artifactory) in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins Pipeline: Upload artifact to Nexus

What will be the output of this Jenkins pipeline snippet when uploading a file to Nexus repository?

Jenkins

pipeline {
  agent any
  stages {
    stage('Upload') {
      steps {
        script {
          sh '''
          curl -v -u admin:admin123 --upload-file myapp.jar \
          http://nexus.example.com/repository/maven-releases/com/example/myapp/1.0/myapp-1.0.jar
          '''
        }
      }
    }
  }
}

A Upload succeeds with HTTP 201 Created status and artifact stored in Nexus

B Upload fails with HTTP 404 Not Found because repository URL is incorrect

C Upload fails with HTTP 401 Unauthorized due to wrong credentials

D Upload succeeds but artifact is stored in Nexus with a wrong version number

💡 Hint

Check the HTTP status code returned by curl and the repository URL correctness.

The curl command uploads the file to the correct Nexus repository URL with valid credentials, so HTTP 201 Created means success.

❓ Troubleshoot

intermediate

Artifact download failure from Artifactory

A Jenkins job tries to download an artifact from Artifactory using this command: curl -u user:pass -O http://artifactory.example.com/artifactory/libs-release-local/com/example/app/1.0/app-1.0.jar The job fails with '404 Not Found'. What is the most likely cause?

A The curl command syntax is invalid and causes failure

B The artifact path or version does not exist in Artifactory

C The Artifactory server is down and not reachable

D The user credentials are incorrect causing access denial

💡 Hint

404 means the resource was not found at the URL.

HTTP 404 means the requested artifact path or version is missing in Artifactory, not a credentials or syntax issue.

❓ Configuration

advanced

Jenkins Declarative Pipeline with Artifactory integration

Which Jenkins pipeline snippet correctly configures Artifactory server and uploads a Maven artifact using the Artifactory plugin?

A

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        rtMavenDeployer(
          id: 'deployer-1',
          releaseRepo: 'libs-release-local',
          snapshotRepo: 'libs-snapshot-local'
        )
        rtMavenRun(
          pom: 'pom.xml',
          goals: 'clean install'
        )
      }
    }
  }
}

B

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        rtMavenDeployer(
          id: 'deployer-1',
          serverId: 'wrong-server',
          releaseRepo: 'libs-release-local',
          snapshotRepo: 'libs-snapshot-local'
        )
        rtMavenRun(
          pom: 'pom.xml',
          goals: 'clean install'
        )
      }
    }
  }
}

C

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        rtMavenDeployer(
          id: 'deployer-1',
          serverId: 'artifactory-server',
          releaseRepo: 'libs-release-local',
          snapshotRepo: 'libs-snapshot-local'
        )
        rtMavenRun(
          pom: 'pom.xml',
          goals: 'clean install'
        )
      }
    }
  }
}

D

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        rtMavenDeployer(
          id: 'deployer-1',
          serverId: 'artifactory-server',
          releaseRepo: 'libs-release-local'
        )
        rtMavenRun(
          pom: 'pom.xml',
          goals: 'clean install'
        )
      }
    }
  }
}

💡 Hint

The serverId must match the configured Artifactory server in Jenkins.

Option C correctly specifies the Artifactory server ID and both release and snapshot repositories, enabling proper upload.

✅ Best Practice

advanced

Secure handling of credentials for Nexus in Jenkins

Which method is the best practice to securely use Nexus credentials in a Jenkins pipeline?

A Store credentials in Jenkins Credentials Manager and reference them with 'credentialsId' in pipeline

B Hardcode username and password directly in the pipeline script for simplicity

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

D Use environment variables set globally on Jenkins master without encryption

💡 Hint

Think about security and ease of credential management.

Jenkins Credentials Manager encrypts and securely stores secrets, which pipelines can access safely using credentialsId.

🔀 Workflow

expert

Automated artifact versioning and deployment workflow with Jenkins and Artifactory

Which Jenkins pipeline workflow correctly implements automatic semantic versioning and uploads the artifact to Artifactory with the new version?

Jenkins

pipeline {
  agent any
  environment {
    ARTIFACTORY_SERVER = 'artifactory-server'
  }
  stages {
    stage('Versioning') {
      steps {
        script {
          def version = sh(script: "git describe --tags --abbrev=0", returnStdout: true).trim()
          def parts = version.tokenize('.')
          def patch = parts[2].toInteger() + 1
          env.NEW_VERSION = "${parts[0]}.${parts[1]}.${patch}"
          echo "New version: ${env.NEW_VERSION}"
        }
      }
    }
    stage('Build and Upload') {
      steps {
        rtMavenDeployer(
          id: 'deployer-1',
          serverId: ARTIFACTORY_SERVER,
          releaseRepo: 'libs-release-local'
        )
        rtMavenRun(
          pom: 'pom.xml',
          goals: "clean install -Drevision=${env.NEW_VERSION}"
        )
      }
    }
  }
}

A The pipeline fails because git describe command is missing in Jenkins environment

B The pipeline uses fixed version from pom.xml and uploads artifact without version change

C The pipeline increments major version incorrectly causing build failure

D The pipeline increments patch version from last git tag, sets it as Maven revision, and uploads artifact to Artifactory

💡 Hint

Check how the version is parsed and incremented, and how it is passed to Maven build.

Option D correctly extracts last git tag, increments patch version, sets it as Maven revision, and uploads artifact with new version.