v2019: Jenkinsfile: Add timeout and retry to be more resilient (!255) · Merge requests · infrastructure / apertis-image-recipes · GitLab

🔴 v2024.3 entered Hard Code Freeze, changes will not be accepted • schedule

🔴 v2025pre entered Hard Code Freeze, changes will not be accepted • schedule

🟠 v2026dev0 entered Soft Code Freeze/Hard Feature Freeze, only bug fixes will be accepted • schedule

Emanuele Aina requested to merge wip/em/v2019-jenkins-retry into apertis/v2019 Jun 01, 2020

After a recent kernel update on the workers we've been hitting issues that cause jobs to get stuck or fail:

fakemachine dying with no trace: https://jenkins.apertis.org/job/apertis-v2020/job/images/job/debos-image-build/151/execution/node/1038/log/
kernel in fakemachine getting stuck in crypto_wait_for_test: https://jenkins.apertis.org/job/apertis-v2019/job/images/job/debos-image-build/299/execution/node/262/log/

Set a timeout to cause the bigger jobs to fail after 30 minutes with no new output in the logs and then tell Jenkins to automatically retry them.

This is a backport of !248 (merged) to the apertis/v2019 branch.

Apertis Website Terms of Use Privacy Policy