[MPT-18998] Increased workflow timeout to 90 minutes#228
Conversation
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughGitHub Actions workflow timeout values are increased from 60 to 90 minutes across four build job configurations in cron-main-e2e.yml, pull-request.yml, push-release-branch.yml, and release.yml. No functional logic or steps are modified. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📝 Coding Plan
Comment |
albertsola
left a comment
There was a problem hiding this comment.
This 90min are becoming scary.
Note: For the PR we don't do E2E anymore so we could lower the timeout



This pull request increases the build job timeout from 60 minutes to 90 minutes across several GitHub Actions workflow files. This change ensures that longer-running builds have sufficient time to complete, reducing the likelihood of jobs failing due to timeout.
CI/CD workflow updates:
timeout-minutesvalue from 60 to 90 for thebuildjob in the following workflow files:.github/workflows/cron-main-e2e.yml.github/workflows/pull-request.yml.github/workflows/push-release-branch.yml.github/workflows/release.ymlCloses MPT-18998
buildjob timeout from 60 to 90 minutes across all workflow files.github/workflows/cron-main-e2e.yml.github/workflows/pull-request.yml.github/workflows/push-release-branch.yml.github/workflows/release.yml