无Manage Jenkins权限时，如何在企业Jenkins中指定特定Maven与JDK构建Java应用

Hey there, let's troubleshoot this Maven build issue step by step—since you're working with a corporate Jenkins instance without admin access, we'll focus on actionable checks you can do yourself first.

First, Verify the Directory & POM File Actually Exist in the Agent Workspace #

The error says Maven can't find the POM, so let's confirm the path and file accessibility first. Add a quick debug step before your Maven command to check what Jenkins sees:

dir("test/test2/project") {
    // Print current directory and list all files
    sh "pwd && ls -la"
    // Then run your Maven command
    sh "mvn clean install -Dmaven.test.skip=true"
}

This will show you exactly which directory Jenkins is in, and whether pom.xml is visible there. If the file doesn't show up, your code probably didn't get pulled into the agent's workspace correctly—double-check your SCM (Git/SVN) configuration in the job to make sure it's cloning the right repo/branch and not failing silently.

Fix the -f Parameter Usage (You Might Have Missed the Build Goals) #

You mentioned trying the -f flag but it didn't work—make sure you include the full build command after specifying the POM path. A partial command like mvn -f /path/to/pom.xml won't execute any actions, since you need to include the goals (clean install):

withEnv(["PATH+MAVEN=${tool 'maven-3.5.0'}/bin:${env.JAVA_HOME}/bin"]) {
    sh "mvn -f /var/jenkins/workspace/test/test2/project/pom.xml clean install -Dmaven.test.skip=true"
}

Confirm the Agent's Maven & JDK Are Properly Loaded #

Even though you're using tool 'maven-3.5.0', we need to make sure the tool name matches what's configured in Jenkins (ask your admin if you're unsure) and that it's accessible on the agent. Add a debug step to verify the environment:

withEnv(["PATH+MAVEN=${tool 'maven-3.5.0'}/bin:${env.JAVA_HOME}/bin"]) {
    sh "echo 'Current Java Home:' \$JAVA_HOME"
    sh "mvn -version" // This should show the correct Maven and Java versions
    sh "mvn -f /var/jenkins/workspace/test/test2/project/pom.xml clean install -Dmaven.test.skip=true"
}

If mvn -version fails, the maven-3.5.0 tool entry might point to a non-existent path on the agent—your admin will need to fix that.

Try Explicitly Changing Directory Before Running Maven #

Sometimes the dir() block in Jenkins doesn't behave as expected (especially if there are permission quirks). Instead, use a cd command directly in the shell to ensure you're in the right folder:

withEnv(["PATH+MAVEN=${tool 'maven-3.5.0'}/bin:${env.JAVA_HOME}/bin"]) {
    sh "cd /var/jenkins/workspace/test/test2/project && mvn clean install -Dmaven.test.skip=true"
}

Check File Permissions (Ask Your Admin for Help Here) #

If all the above steps confirm the POM exists but Maven still can't read it, the Jenkins user running the job on the agent might not have read permissions for the pom.xml file or its parent directories. Ask your admin to check the permissions on /var/jenkins/workspace/test/test2/project and ensure the Jenkins service user has read access to the file.

Final Check: Ensure the Agent Workspace Is Synced #

If your job uses a shared or cached workspace, sometimes old or incomplete files can cause issues. Ask your admin to clear the agent's workspace for your job, then re-run the build to pull fresh code.

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