Amplify-console: Amplify fails during deploy phase without any error log.

[leelakrishnachava]

The final log of the deploy phase. I can provide more information on need basis.

2020-03-03T19:39:34 [INFO]: Skipping upload of existing file tsconfig.json
2020-03-03T19:39:34 [ERROR]: Failed to deploy
2020-03-03T19:39:34 [INFO]: Deployment finished.

1. I have removed tests and tried to deploy. Didn't work.
2. I tried with successful previous build version. fails with same error.

Our App ARN: arn:aws:amplify:eu-central-1:527787139714:apps/d2m8o2kz3kftbw

[nimacks]

@leelakrishnachava , it looks like your subsequent builds 190, 191,192 succeeded. The error was due to a transient error. Please confirm that your builds are now working.

[leelakrishnachava]

@nimacks it is the deploy phase that fails. builds are always successful. our development team is blocked because of this issue. Please help.

Also sometimes, this deploy phase, I get a lot of logs like "uploading of existing file" as mentioned below and the pipeline hangs.

2020-03-05T02:09:39 [INFO]: Skipping upload of existing file amplify/backend/function/QueryCryptoOrderStatus/src/node_modules/@hapi/hoek/lib/isPromise.js
2020-03-05T02:09:39 [INFO]: Skipping upload of existing file amplify/#current-cloud-backend/function/CommandCryptoOrder/src/node_modules/@hapi/hoek/lib/merge.js
2020-03-05T02:09:39 [INFO]: Skipping upload of existing file amplify/backend/function/QueryCryptoOrderStatus/src/node_modules/@hapi/hoek/lib/once.js
2020-03-05T02:09:39 [INFO]: Skipping upload of existing file amplify/#current-cloud-backend/function/QueryCryptoOrderStatus/src/node_modules/@hapi/hoek/lib/reach.js
2020-03-05T02:09:39 [INFO]: Skipping upload of existing file amplify/#current-cloud-backend/function/QueryCryptoOrderStatus/src/node_modules/@hapi/hoek/lib/reachTemplate.js
2020-03-05T02:09:39 [INFO]: Skipping upload of existing file amplify/backend/function/QueryCryptoOrderStatus/src/node_modules/@hapi/hoek/lib/stringify.js
2020-03-05T02:09:39 [INFO]: Skipping upload of existing file amplify/backend/function/CommandCryptoOrder/src/node_modules/@hapi/hoek/lib/types.js
2020-03-05T02:09:39 [INFO]: Skipping upload of existing file amplify/backend/function/CommandCryptoOrder/src/node_modules/@hapi/hoek/lib/utils.js
2020-03-05T02:09:39 [INFO]: Skipping upload of existing file amplify/backend/function/CommandCryptoOrder/src/node_modules/@hapi/hoek/lib/wait.js
2020-03-05T02:09:39 [INFO]: Skipping upload of existing file amplify/backend/function/CommandCryptoOrder/src/node_modules/@hapi/hoek/LICENSE.md

Looking forward for your help.

[leelakrishnachava]

Latest ARN app pipeline for reference.

arn:aws:amplify:eu-central-1:977140504228:apps/d11qo675ovmo7d

[brettcat]

Here is another pipeline that won't run in a container on amplify but works perfectly in the same container not on amplify.
arn:aws:amplify:us-east-1:121121043565:apps/dyyavgxnxcfcm

This tries to use pa11y-ci, forking gatsby serve & first in the preTest phase.

Now, even though there's a test section in the amplify.yml file in the root of the repo, the tests are still being skipped.

[kahdojay]

@leelakrishnachava can you share a recent build number where this happens and the branch you're attempting to deploy?

[simpson]

+1 Our team is experiencing this very frequently the past few days, yet no outages have been reported for Amplify

https://github.com/aws-amplify/amplify-console/issues/541

[thapakazi]

+1
Ditto, Same for my team multiple projects :( can you help unblock our devs ?
Can I get your email or something to send my account/projects details. Thanks

[nimacks]

@leelakrishnachava @simpson @thapakazi, we've made enhancements to our deploy service which will resolve the issues mentioned. Are you still running into this issue?

[simpson]

The new deploy mechanism is a game changer, everything clear for me

[simpson]

@swaminator @nimacks @litwicki Have any additional patches gone out? Our production app at designed.org is down

[nimacks]

Hi @simpson, i'm able to access designed.org. are you still having an issue?

[litwicki]

@simpson can you confirm this is no longer an issue?