Debugging build failure in CI/CD with Jenkins

 Replacing java17 with java 11 for maven builds

Isolation of ENVIRONMENTS and Troubleshooting:
1. Dev - VPC  - openjdk 11
mvn clean package - success

2. QA - VPC - openjdk 11
mvn clean package - success

3. UAT - VPC - openjdk 11
mvn clean package - success

Communication gap

4. Prod - VPC - openjdk 17    # issue,application failed in Prod

mvn clean package – failed

Step in Troubleshooting:

Identify or Discovery of the problem – log/metrics

Check console output fo logs.

Search for error pipe and grep or filter logs for errors and exceptions.

 Error …Java 17 was not compactible for that webapp build to build.

Use Mindspark(GPT compactible)if available in the environment, to identify the problem.

Escalate a ticket to the team members. This is very important because IT is a collaboration industry.

twtech Recommended escalation path: Team members, Senior Engineers, and Managers.

When solution is found, go ahead and test the solution.

Standard Operation Procedure:

Testing the solution is only permitted to the Dev environment.

Testing a solution in QA, UAT  can bring major disruptions.

On no situation should testing ever be done in the Prod. If it fails, there would be outages and major  blow to N-users traffic.

Recommendation:

Apply the solution in the test environment, monitor/observe and see if all goes well, then  deploy in the QA, UAT and Prod.

Solution Command:

sudo yum remove java* -y

sudo yum update -y

sudo yum install openjdk-11-jre -y