Jenkins无法与按文件夹组织的Git仓库协同工作问题求助

Hey there! Let’s walk through the most common reasons your Jenkins build isn’t generating those expected .class files, and how to fix them step by step:

• Verify your source path configuration in Jenkins
  Since your repo is split into separate folders (code vs .tex), Jenkins might not be targeting the right directory for compilation. Check your job’s Source Code Management settings—if your Java source files live in a subfolder like ./code-folder, make sure Jenkins is checking out the entire repo, and your build steps are running from the correct working directory. For example, add a pre-compilation step to navigate to the code folder:

  cd ./your-code-subfolder
  

• Double-check your build commands
  If you’re using manual compilation (like javac), ensure you’re specifying an output directory with the -d flag—otherwise, .class files will end up in the same folder as your .java files instead of a dedicated build directory. A proper command might look like:

  javac -d ./build/classes src/**/*.java
  

  If you’re using build tools like Maven or Gradle, confirm you’re running the correct lifecycle commands (e.g., mvn clean install or gradle build), and that your pom.xml/build.gradle is configured to output classes to the expected directory.

• Confirm the full repo is being pulled
  Even if Jenkins recognizes the repo, it might not be pulling all folders. Head to your Jenkins workspace directory (usually under /var/lib/jenkins/workspace/your-job-name on Linux) and check if your code folder exists and contains all the .java files you need. Also, make sure your .gitignore file isn’t accidentally excluding source files or the build directory.

• Dig into the Jenkins build logs
  This is your best resource! Go to your job’s build history, click into the failed/partial build, and check the Console Output. Look for errors like:

  javac: file not found: src/*.java
  [ERROR] COMPILATION ERROR :
  These will tell you exactly where the breakdown is—whether it’s missing source files, incorrect paths, or dependency issues.

• Check workspace permissions
  On Linux/macOS, the Jenkins user (typically jenkins) needs write permissions to create the build directory and output .class files. You can add a quick step to your build pipeline to verify:

  mkdir -p ./build/classes
  ls -ld ./build
  

  If you see permission denied errors, you’ll need to adjust the workspace folder’s ownership or permissions.

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