Investigate CI Build Timeout Error on 3/7/2024

[gracekretschmer-metrostar]

User Story or Problem Statement

To prevent the daily deploy to be blocked again and improve the health of CI build, the CMS needs to understand why the CI build is taking longer than 60 minutes to complete the process and explore opportunities to reduce the processing time.

Description or Additional Context

On 3/7/2024, the daily deploy failed because of a timeout error with the CI build, so the CMS team extended the time limit from 60 minutes to 120 minutes and the daily deploy was successful run. The CMS team's hypothesis is that the how efficiently the runners are being user could be a source of the delay.

Steps for Implementation

• [ ]

Acceptance Criteria

• [ ] Understand why the CI build is taking longer than 60 minutes to complete the process.
• [ ] A plan of action to reduce the CI build time and, in turn, improve the health of CI build.

Team

Please check the team(s) that will do this work.

• [x] CMS Team
• [ ] Public Websites
• [ ] Facilities
• [ ] Accelerated Publishing

[7hunderbird]

In retrospect one of the ways these builds will seem to hang and "timeout" have been around the GitHub runners and a disk space issue that Tim is working on rolling out the fix that will keep the GitHub Action runners from having too little disk space.

And so I think we know the root cause and fix now and this ticket can be closed.