👀 Views: 5484 💬 Answers: 1 📅 Created: 2025-09-21

java jenkins ci-cd legacy-code maven Java

I'm working through a tutorial and I can't seem to get I've been banging my head against this for hours..... Currently developing a CI/CD pipeline for a legacy Java application running on Jenkins 2.319. The pipeline frequently fails during the build phase, often with unclear errors. For instance, one recent failure log included: ``` ERROR: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project myapp: Compilation failure: Compilation failed: [ERROR] /var/lib/jenkins/workspace/myapp/src/main/java/com/example/MyClass.java:[25,8] [ERROR] cannot find symbol ``` Upon investigating, I discovered that the application relies on some deprecated dependencies, like JUnit 4.12 and Spring Framework 4.3. While upgrading these dependencies would typically be a good move, I'm hesitant since the application has many entangled configurations that aren't well-documented. I tried adjusting the `pom.xml` to include the correct versions for the Maven dependencies: ```xml <dependency> <groupId>org.springframework</groupId> <artifactId>spring-core</artifactId> <version>5.3.10</version> </dependency> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>5.7.2</version> <scope>test</scope> </dependency> ``` However, the build still fails, and the logs contain a mix of compilation errors and runtime warnings that pile up. To tackle this problem, I attempted to isolate the failing tests using the following command: ```bash mvn test -Dtest=MyClassTest ``` This helped identify that some tests are using old APIs that no longer exist in the newer Spring version. I considered using the `maven-surefire-plugin` to skip certain tests temporarily, but that feels like a hack rather than a fix. Documentation suggests using the `Jenkinsfile` to streamline the build process, where I might be able to incorporate environmental variables to manage configurations better: ```groovy pipeline { agent any environment { MAVEN_OPTS = '-Xmx1024m' } stages { stage('Build') { steps { sh 'mvn clean package' } } } } ``` Still, I’m unsure whether the problem stems from Jenkins itself or the underlying project structure. Has anyone experienced similar issues when updating legacy Java applications in Jenkins? Any strategies for identifying and resolving these compilation errors or optimizing the CI/CD process would be tremendously helpful. Has anyone else encountered this? I'm working with Java in a Docker container on Linux. I appreciate any insights! For context: I'm using Java on Windows 10. Any ideas how to fix this?