如何通过Jenkinsfile指定仓库文件夹构建（无Jenkins UI权限）

Hey there! I get that you can't tweak Jenkins UI settings and have to stick with the Jenkinsfile to switch your build source from the default workspace to a specific folder in your repo. No worries—here are two reliable approaches to make this happen:

方法1：使用dir()步骤（推荐，灵活） #

This is the most straightforward way, especially if you only need to run certain build steps within the target folder. The dir() step lets you change the working directory for a block of steps, without altering the global workspace.

Example Jenkinsfile:

pipeline {
    agent any
    stages {
        stage('Build from Target Folder') {
            steps {
                // Switch to the specific folder inside your cloned repo
                dir('path/to/your/target-folder') {
                    // Verify the current directory (optional, for debugging)
                    sh 'echo "Current working directory: $(pwd)"'
                    
                    // Run your build commands here—they'll execute inside the target folder
                    sh 'mvn clean install' // Replace with your actual build command, like npm run build, gradle build, etc.
                }
            }
        }
    }
}

Why this works: When you wrap steps in dir(), Jenkins will automatically navigate to that subdirectory relative to the default workspace (where your repo is cloned) before executing the enclosed commands. Once the block finishes, it'll switch back to the original workspace.

方法2：设置全局自定义工作区（适合全流水线场景） #

If every step in your pipeline needs to run inside the target folder, you can configure a custom workspace directly in the agent block. This changes the working directory for the entire pipeline run.

Example Jenkinsfile:

pipeline {
    agent {
        node {
            label 'your-agent-label' // Replace with your actual agent/runner label
            customWorkspace "${WORKSPACE}/path/to/your/target-folder"
        }
    }
    stages {
        stage('Full Pipeline in Target Folder') {
            steps {
                sh 'echo "Current working directory: $(pwd)"'
                sh 'npm run build' // Your build command here
            }
        }
    }
}

Note: ${WORKSPACE} is a built-in Jenkins variable that points to the default workspace directory (where your repo is cloned). By appending your target folder path to it, you tell Jenkins to use that subdirectory as the primary workspace for the pipeline.

关键注意事项 #

• Double-check that the target folder actually exists in your repo—Jenkins will throw an error if it tries to navigate to a non-existent directory.
• For multi-branch pipelines, this setup works seamlessly since each branch is cloned to its own workspace, and the target folder path is relative to that branch's root.
• If your build commands rely on paths outside the target folder, make sure to use absolute paths or adjust the commands accordingly when using these methods.

内容的提问来源于stack exchange，提问作者Prateek S