- Newest
- Most votes
- Most comments
Hi @simon, We can definitely help in increasing the timeout, will let you know once the timeout is increased across all regions so you can retry this service again. Thanks
Hi Hari, yeah it can take quite a while, depends on the machine it's running on. For comparison, on github actions:
- Run test pipeline / build core packages (pull_request) Successful in 5m
- Run test pipeline / Build website-app and run tests (pull_request) Successful in 10m
there it takes 15 minutes in total (with a cache though).
Is there any possibility to modify the timeout?
Hi @simon, We have increased the timeout and the change is promoted across all regions, can you please give it a try and let us know
In this case, the build stage took more than 19 mins to complete which has caused the service creation to fail, possibly because the build is executing some custom script or running unit tests which is taking much longer to complete.
Question to @simllll [customer] - When you tested this locally how long did it to take to complete the execution of the build command? I am assuming we are using this command?
npm install && npm run build
Relevant content
- asked 2 years ago
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Looking foward to it already :) thanks
Hi @simon, We have increased the timeout and the change is promoted across all regions, can you please give it a try and let us know