aws-amplify / aws-amplify/amplify-hosting
Build settings UI states max build time is 8 hours
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
### Before opening, please confirm:
- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.
### App Id
N/A
### AWS Region
us-east-2
### Amplify Hosting feature
Build settings
### Frontend framework
Next.js
### Next.js version
13
### Next.js router
App Router
### Describe the bug
The build settings UI states "The maximum build timeout is 8 hours." However if you try to save anything higher than 120 minutes, it says "Updating build settings failed. Build timeout cannot exceed 120 minutes."
I have a project that needs to build 2738 SSR pages. The build is expected to take very close to 120 minutes and possibly slightly more. If I cannot extend my build timeout beyond 120 minutes, Ampllify may not work for me. Maybe it could be a quota that defaults to 120 but could be increased.
### Expected behavior
Entering 480 minute build timeout should work based on stated 8-hour maximum.
### Reproduction steps
1. Open build settings.
2. Note that it says "The maximum build timeout is 8 hours."
3. Try to enter a value higher than 120 minutes and save
### Build Settings
_No response_
### Log output
```
# Put your logs below this line
```
### Additional information
_No response_
Contributor guide
Research direction
Start by reproducing the mismatch in the Build settings UI: compare the displayed eight-hour maximum with the validation error when saving a value above 120 minutes. Trace the setting's validation and update path, then confirm that the accepted limit and displayed guidance agree, including the reported 480-minute value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- next.js
- Domain
- build-system, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100