aws-amplify / aws-amplify/amplify-hosting
'Next.js - SSR' deploy success but doesn't applied and redeploy doesn't work.
- 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 questions](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have removed any sensitive information from my code snippets and submission.
### App Id
d3rj4gq78a5ct0
### AWS Region
ap-southeast-1
### Amplify Hosting feature
Frontend builds
### Question
I have 'Next.js - SSR' project that deployed successful but the change of deployment doesn't applied and after every feature branches that had been deployed get the same results that is not the code of that branch. I tried redeploy older version of code that previously worked but it deployed successful but the website doesn't change back to the older version.
File: amplify.yml
```
version: 1
applications:
- frontend:
phases:
preBuild:
commands:
- npm ci
build:
commands:
- npm run build
artifacts:
baseDirectory: .next
files:
- '**/*'
cache:
paths:
- 'node_modules/**/*'
appRoot: project-name
```
Contributor guide
Research direction
Start with amplify.yml and the Next.js SSR frontend-build configuration, then compare the deployed output for the reported feature branches and older revision. Check the associated Amplify build and deployment results to determine whether the current branch code is being published. Done means a successful deployment serves the code from the selected revision and redeploying an older revision changes the site accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, next.js
- Domain
- ci-cd, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100