Can a stage has multiple steps?

Question

Accepted Answer

A stage in a Jenkins Pipeline can absolutely contain multiple steps. In fact, this is a fundamental feature that allows stages to represent meaningful phases of work (like 'Build' or 'Test') while steps define the individual actions that accomplish that phase. Each step within a stage executes sequentially, and you can include any number of steps—from simple echo statements to complex script blocks. The official Jenkins documentation emphasizes that a stage must contain at least one step, but there's no upper limit on how many steps you can include. pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                echo 'Starting build process...'
                sh 'mvn clean compile'
                sh 'npm install'
                sh 'npm run build'
                echo 'Build completed successfully'
            }
        }
    }
}

// This Build stage contains five sequential steps:
// echo → compile Java → install Node deps → build frontend → final echo Grouping multiple steps within a stage serves several important purposes. It improves pipeline visualization because Jenkins shows each stage as a single block in the UI, with its overall status and duration. This makes pipelines easier to understand than having a separate stage for every tiny action. It also allows you to apply stage-level directives like `when` conditions, `environment` variables, or `tools` configurations that apply to all steps within that stage. If any step fails, the entire stage fails, providing clear error isolation. pipeline {
    agent any
    environment {
        TEST_HOME = '/opt/test-framework'
    }
    stages {
        stage('Test') {
            when {
                branch 'develop'  // Only run tests on develop branch
            }
            steps {
                // Multiple steps with different purposes
                sh 'npm run lint'
                sh 'npm run test:unit'
                sh 'npm run test:integration'
                junit 'test-results/*.xml'
                archiveArtifacts artifacts: 'coverage/**', fingerprint: true
                echo 'All tests passed!'
            }
            post {
                failure {
                    slackSend(
                        color: 'danger',
                        message: "Tests failed in ${env.JOB_NAME} - ${env.BUILD_URL}"
                    )
                }
            }
        }
    }
}

// This stage contains 6 steps that run sequentially:
// lint → unit tests → integration tests → publish results → archive → log
// All steps share the same `when` condition and environment Steps within a stage execute in the order they are written, and each step runs to completion before the next begins. Steps can be built-in (like `sh`, `echo`), come from plugins (like `junit`, `slackSend`), or be custom steps defined in shared libraries. The pipeline will stop executing further steps within the same stage if a step fails (unless you've configured error handling). This sequential execution makes the flow predictable and easy to debug—logs clearly show which step succeeded or failed. The distinction between stages and steps is a key design principle in Jenkins Pipeline. Stages provide the high-level structure and visualization—they should represent meaningful phases that stakeholders can understand. Steps provide the detailed execution—they are the actual commands that do the work. A well-designed pipeline typically has a handful of stages (Checkout, Build, Test, Deploy) with multiple steps inside each stage. This balance keeps pipelines readable while allowing complex automation . stage('Complex Process') {
    steps {
        script {
            try {
                sh 'first-command'
                sh 'second-command'
                sh 'third-command'
            } catch (Exception e) {
                echo "Error occurred: ${e.message}"
                // Custom error handling
                sh './cleanup.sh'
                error 'Pipeline stopped' // Rethrow to mark stage failed
            }
        }
    }
}

// Even within multiple steps, you can wrap them in script blocks
// for custom error handling and flow control

Can a stage has multiple steps?

Yes, a stage in Jenkins Pipeline can contain multiple steps that execute sequentially within that stage, allowing complex workflows to be organized into logical units

Can a stage has multiple steps?

Yes, a stage in Jenkins Pipeline can contain multiple steps that execute sequentially within that stage, allowing complex workflows to be organized into logical units

Scenario Questions

Follow-up Questions