Update github action for deployment robustness #419
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add timeouts to stop never ending jobs eating up all our github credits - Ensure different branches / executions use a different artefact
poespas
approved these changes
Oct 20, 2025
Collaborator
|
Thanks! ✨ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Timeouts
Added some generous timeouts to the build and deployment steps. I would realistically think these should be lower but some instances are tough.
If anyone is onboarding on to hypernode and they find 60 minutes is not enough, it should be a simple task to increase the timeout. At least having them here ensures they're being considered?
Not having these could leave them running for a lot longer, which can chew up our github credit allowance and cost more money