Skip to content

Commit ca94851

Browse files
committed
fix(ci): Add an immediate try at maven deployment check
When the job is retried, we don’t want to wait for 5m before the first try.
1 parent 95de525 commit ca94851

1 file changed

Lines changed: 10 additions & 5 deletions

File tree

.gitlab-ci.yml

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1017,11 +1017,12 @@ verify_maven_central_deployment:
10171017
"https://repo1.maven.org/maven2/com/datadoghq/dd-trace-api/${VERSION}/dd-trace-api-${VERSION}.jar"
10181018
"https://repo1.maven.org/maven2/com/datadoghq/dd-trace-ot/${VERSION}/dd-trace-ot-${VERSION}.jar"
10191019
)
1020-
# Wait 5 mins initially, then try 5 times with a minute delay between each retry to see if the release artifacts are available
1021-
sleep 300
1020+
# Try once immediately (fast path on job retry), then wait 5 mins for initial propagation,
1021+
# then try 4 more times with a minute delay between each retry.
10221022
TRY=0
1023-
MAX_TRIES=5
1024-
DELAY=60
1023+
MAX_TRIES=6
1024+
INITIAL_DELAY=300
1025+
RETRY_DELAY=60
10251026
while [ $TRY -lt $MAX_TRIES ]; do
10261027
ARTIFACTS_AVAILABLE=true
10271028
for URL in "${ARTIFACT_URLS[@]}"; do
@@ -1038,7 +1039,11 @@ verify_maven_central_deployment:
10381039
echo "The release was not available after 10 mins. Manually re-run the job to try again."
10391040
exit 1
10401041
fi
1041-
sleep $DELAY
1042+
if [ $TRY -eq 1 ]; then
1043+
sleep $INITIAL_DELAY
1044+
else
1045+
sleep $RETRY_DELAY
1046+
fi
10421047
done
10431048
10441049
publishing-gate:

0 commit comments

Comments
 (0)