Increase timeout for CI/CD jobs

[seanbudd]

Link to issue number:

Follow up to #19209

Summary of the issue:

We added a 10min time limit to cap and measure builds.
This was just too low, as a recent build narrowly timed out.

A similar cap for the create launcher step also is timing out: https://github.com/nvaccess/nvda/actions/runs/19415041964

Description of user facing changes:

none

Description of developer facing changes:

builds shouldnt timeout unexpectedly

Description of development approach:

increase build timeout to 15min and launcher timeout to 30min

Testing strategy:

run CI/CD

Known issues with pull request:

none

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.

[wmhn1872265132]

The timeout for Create launcher should also be increased, here step took 26 minutes

[seanbudd]

@wmhn1872265132 - wow that is much higher than usual. Do you know of any other examples of this occurring, or is that just a one off?

[wmhn1872265132]

And here

[seanbudd]

Thanks for the examples @wmhn1872265132 - I've upped the limit to 30min

[Copilot]

Pull Request Overview

This PR increases the timeout limits for CI/CD workflow jobs to prevent unexpected build timeouts following a recent build that narrowly exceeded the previous 10-minute limit.

Key changes:

• Increased Build NVDA job timeout from 10 to 15 minutes
• Increased Create launcher job timeout from 20 to 30 minutes

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.