Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First time deployment failed with Error: Command failed with exit code 1 #2285

Open
Lame-Dolphin opened this issue Nov 30, 2024 · 2 comments
Labels
console-builds Issues related to Amplify console builds pending-community-response Issue is pending a response from the author or community question Question or confusion about some aspect of the product

Comments

@Lame-Dolphin
Copy link

Environment information

0

2024-11-30T17:47:39.964Z [INFO]: # Cloning repository: [email protected]:Lame-Dolphin/inventory-management.git

1

2024-11-30T17:47:41.895Z [INFO]:

2

2024-11-30T17:47:41.896Z [INFO]: Cloning into 'inventory-management'...

3

2024-11-30T17:47:41.896Z [INFO]: # Checking for Git submodules at: /codebuild/output/src2378526957/src/inventory-management/.gitmodules

4

2024-11-30T17:47:41.906Z [INFO]: # Retrieving environment cache...

5

2024-11-30T17:47:41.942Z [WARNING]: ! Unable to write cache: {"code":"ERR_BAD_REQUEST","message":"Request failed with status code 404"})}

6

2024-11-30T17:47:41.942Z [INFO]: ---- Setting Up SSM Secrets ----

7

2024-11-30T17:47:41.942Z [INFO]: SSM params {"Path":"/amplify/dkqunsg23t9md/master/","WithDecryption":true}

8

2024-11-30T17:47:41.994Z [WARNING]: !Failed to set up process.env.secrets

9

2024-11-30T17:47:42.815Z [INFO]: # No package override configuration found.

10

2024-11-30T17:47:42.818Z [INFO]: # Retrieving cache...

11

2024-11-30T17:47:42.856Z [INFO]: # Retrieved cache

12

2024-11-30T17:47:46.080Z [INFO]: ## Starting Backend Build

13

## Checking for associated backend environment...

14

## No backend environment association found, continuing...

15

## Completed Backend Build

16

2024-11-30T17:47:46.085Z [INFO]: {"backendDuration": 0}

17

## Starting Frontend Build

18

# Starting phase: preBuild

19

# Executing command: npm ci --cache .npm --prefer-offline

20

2024-11-30T17:47:58.754Z [WARNING]: npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported

21

2024-11-30T17:47:59.411Z [WARNING]: npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

22

2024-11-30T17:48:00.714Z [WARNING]: npm WARN deprecated

23

2024-11-30T17:48:00.715Z [WARNING]: @humanwhocodes/[email protected]: Use @eslint/object-schema instead

24

2024-11-30T17:48:00.717Z [WARNING]: npm

25

2024-11-30T17:48:00.718Z [WARNING]: WARN deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead

26

2024-11-30T17:48:01.312Z [WARNING]: npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported

27

2024-11-30T17:48:02.445Z [WARNING]: npm WARN deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.

28

2024-11-30T17:48:10.235Z [INFO]: added 491 packages, and audited 492 packages in 17s

29

2024-11-30T17:48:10.240Z [INFO]: 152 packages are looking for funding

30

run `npm fund` for details

31

found 0 vulnerabilities

32

2024-11-30T17:48:10.253Z [INFO]: # Completed phase: preBuild

33

# Starting phase: build

34

2024-11-30T17:48:10.254Z [INFO]: # Executing command: npm run build

35

2024-11-30T17:48:10.579Z [INFO]: > [email protected] build

36

> next build

37

2024-11-30T17:48:11.213Z [INFO]: ⚠ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache

38

2024-11-30T17:48:11.230Z [INFO]: Attention: Next.js now collects completely anonymous telemetry regarding usage.

39

2024-11-30T17:48:11.231Z [INFO]: This information is used to shape Next.js' roadmap and prioritize features.

Describe the bug

First time deploying but unable to proceed. New to AWS. Do let me know what is the reason for such issue.

Reproduction steps

Link amplify app and tried to deploy.

@Lame-Dolphin Lame-Dolphin added the pending-triage Incoming issues that need categorization label Nov 30, 2024
@ykethan ykethan added the console-builds Issues related to Amplify console builds label Dec 2, 2024
@ykethan
Copy link
Member

ykethan commented Dec 2, 2024

Hey @Lame-Dolphin, thank you for reaching out. To further dive into the issue, could you provide us the App-id and region of the application deployed?

@ykethan ykethan added pending-response Issue is pending response from author pending-community-response Issue is pending a response from the author or community labels Dec 2, 2024
@Jay2113
Copy link

Jay2113 commented Dec 13, 2024

@Lame-Dolphin 👋 , following up here to see if your deployments are unblocked?

@Jay2113 Jay2113 added question Question or confusion about some aspect of the product and removed pending-triage Incoming issues that need categorization pending-response Issue is pending response from author labels Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
console-builds Issues related to Amplify console builds pending-community-response Issue is pending a response from the author or community question Question or confusion about some aspect of the product
Projects
None yet
Development

No branches or pull requests

3 participants