##Need to solve ⚠️
28 messages · Page 1 of 1 (latest)
Helper please have a look, thanks.
Here is an AI assisted attempt to answer your question 🤖. Maybe it helps! In any case, a human is on the way 👍. To continue talking to the AI, you can use </chatgpt:1108714622413963314>.
When you get an unstable build in Jenkins, the cause can vary widely—from test failures, environment issues, to configuration problems. To solve this, start by checking the Jenkins build logs carefully for specific errors or failed tests. Unstable often means some tests failed but the build did not entirely break.
Key steps:
- Review Console Output: Identify exact test failures or warnings.
- Check Test Reports: See which tests consistently fail.
- Validate Build Environment: Ensure dependencies and environment variables are correctly set.
- Check Jenkins Plugins: Sometimes outdated plugins cause instability.
- Try Isolating Tests: Run failing tests locally or in isolation.
- Adjust Build Scripts: If flaky tests or race conditions exist, consider adding retries or stabilization steps.
Unstable builds usually indicate quality issues in the build pipeline, so the goal is to detect root causes rather than just suppress errors.
Useful links:
ull have to share some details if u expect anyone to be able to help u 🙂
But test case are passed in runtime
again, if u dont share the full error messages plus the code we cant really do anything
ur walking into a car mechanic shop "my car is broken, i dont have my car with me though"
"okay, come back with the car then"
I uploaded your attachments as Gist. This makes them more accessible, for example to mobile users.
Caused by: org.springframework.web.client.HttpClientErrorException$BadRequest: 400 Bad Request
Caused by: org.springframework.web.client.HttpServerErrorException$ServiceUnavailable: 503 status 503
its probably not set up correctly on the jenkins build
"it works on my machine" was never a good excuse
u probably did sth on ur machine that u didnt do on the jenkins
(setup a docker instance to get rid of such problems in the future, once and for all)
i bet if u would ask a friend to run it on their machine it wouldnt work either
com.opl.msmeos.profile.common.exception.ExternalServiceException: Invalid OTP
ur log is just full with connection problems rooted in authorization issues
the auth isnt setup right
I'm not so certain those stacktraces are your issues. Above those exceptions it says [INFO] Running Earth downstream error handling — end-to-end client responses, which suggests the tests are purposefully causing failures to check that the app handles them correctly. If it is tests failing then you need to look for Failures: N where N > 0.
It looks like you've cut off the logs when you saw those stacktraces