Managing Multi‑Platform Build Environments with Jenkins Lockable Resources Plugin

In daily development work, teams often need to switch among many platforms (Linux, AIX, Windows, Solris, HP‑UX) and different software versions, but limited virtual machines make it impossible to provision a dedicated VM for every build and test, leading to long setup times.

The analysis shows that Docker cannot satisfy the requirement because it only supports Linux and Windows, and the Artifactory service is temporarily unavailable, so the only viable solution is to build from source code while managing resource contention through locking.

The article introduces Jenkins' Lockable Resources Plugin as the mechanism to lock a VM when a job starts and release it after completion, preventing other jobs from using the same node simultaneously.

Demo steps include:

Configuring lockable resources in Jenkins global settings.

Viewing the resource pool, which initially shows two free resources.

Running parameterized jobs that select different platforms and repositories, observing how the first job locks a resource, the second job waits, and a third job is blocked until a resource is released.

Releasing a locked resource manually and confirming that the waiting job proceeds successfully.

The core of the solution is a Jenkins pipeline that uses the lock step and an input prompt to hold the lock until a user confirms completion. The full Jenkinsfile is shown below:

pipeline {
    agent {
        node {
            label 'PreDevENV'
        }
    }
    options {
        lock(label: 'PreDevENV', quantity: 1)
    }
    parameters {
        choice(name: 'platform', choices: ['Linux', 'AIX', 'Windows', 'Solris', 'HP-UX'], description: 'Required: which platform do you want to build')
        choice(name: 'repository', choices: ['repo-0.1', 'repo-1.1', 'repo-2.1', 'repo-3.1', 'repo-4.1'], description: 'Required: which repository do you want to build')
        string(name: 'branch', defaultValue: '', description: 'Required: which branch do you want to build')
    }
    stages {
        stage('git clone') {
            steps {
                echo "git clone source"
            }
        }
        stage('start build') {
            steps {
                echo "start build"
            }
        }
        stage('install build') {
            steps {
                echo "installing"
            }
        }
        stage('unlock your resource') {
            steps {
                input message: "do you have finished?"
                echo "Yes, I have finished"
            }
        }
    }
}