MLE-25073 Telling Jenkins to wait longer for MarkLogic #574
Conversation
|
Copyright Validation Results ⏭️ Skipped (Excluded) Files
✅ All files have valid copyright headers! |
There was a problem hiding this comment.
Pull Request Overview
This PR increases the timeout configuration for MarkLogic availability checks in Jenkins CI environments to address intermittent timing issues during deployment.
Key Changes:
- Increased the mlWaitTillReady max attempts from default (60) to 40 explicit attempts
- Added an additional mlWaitTillReady check with a 3-second sleep in the Jenkins pipeline
- Updated the net.saliman.properties plugin from version 1.5.2 to 1.6.0
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| test-app/build.gradle | Configured mlWaitTillReady with 40 max attempts and upgraded properties plugin to 1.6.0 |
| Jenkinsfile | Added sleep and duplicate mlWaitTillReady call to ensure MarkLogic availability before deployment |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| apply plugin: "com.marklogic.ml-gradle" | ||
|
|
||
| // Sometimes, 3 x 20 isn't enough on Jenkins. |
There was a problem hiding this comment.
The comment references '3 x 20' but the code sets maxAttempts to 40. This creates confusion about the actual timeout calculation. Update the comment to accurately reflect the new configuration, such as '// Sometimes, the default timeout isn't enough on Jenkins, so increasing to 40 attempts.'
| // Sometimes, 3 x 20 isn't enough on Jenkins. | |
| // Sometimes, the default timeout isn't enough on Jenkins, so increasing to 40 attempts. |
rjrudin
force-pushed
the
feature/jenkins-tweak
branch
from
1b1ed0a to
5920f46
Compare
|
No description provided.