aws-amplify / aws-amplify/amplify-hosting

Deployments failing with no error message

Open
#1,784 3 comments 2 reactions 0 assignees View on GitHub
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-console/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-console/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-console/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### Describe the bug

This is the only message I see in my deployment step:

```
2021-04-28T23:05:35 [INFO]: Starting Deployment
2021-04-28T23:05:35 [ERROR]: Failed to deploy
```

This is happening for my qa and prod environments. I tried disconnecting the branch and reconnecting, deploying old version, redploying. It just keeps getting to the deployment stage and not giving me any info. Just failinh

### Expected behavior

To either deploy the app successfully or give a more descriptive message

### Reproduction steps

1. Go to my amplify application
2. Click redeploy this version

### Build Settings

```yaml
version: 0.1
backend:
phases:
build:
commands:
- '# Execute Amplify CLI with the helper script'
- amplifyPush --simple
frontend:
phases:
preBuild:
commands:
- yarn install
build:
commands:
- yarn run build:$USER_BRANCH
artifacts:
baseDirectory: build
files:
- '**/*'
```

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the deployment-stage log output and the repository build settings, especially amplifyPush, yarn install, and yarn run build:$USER_BRANCH. Reproduce the failure by selecting “redeploy this version” for the QA or production environment. Done means the deployment succeeds or reports a descriptive error instead of only “Failed to deploy.”

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
ci-cd, cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.