You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have removed any sensitive information from my code snippets and submission.
Amplify Hosting feature
E2E Cypress tests
Is your feature request related to a problem? Please describe:
It looks like with Amplify 2, build artifacts can only be downloaded for successful builds, not failing builds. However, they are the most useful to us to troubleshoot things when our E2E tests are failing before deploying, therefore we need to be able to access them for failed builds too.
Describe how you'd like this feature to work
Same as for successful builds but for failed builds too.
We can even see in the logs for failed builds that the artifacts are indeed uploaded to your S3 bucket https://aws-amplify-prod-[region]-artifacts.s3.[region].amazonaws.com/[app_id]/[branch]/000000[build_number]/BUILD/artifacts.zip, so it's not like they were not existing at all.
The text was updated successfully, but these errors were encountered:
This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!
Before opening, please confirm:
Amplify Hosting feature
E2E Cypress tests
Is your feature request related to a problem? Please describe:
It looks like with Amplify 2, build artifacts can only be downloaded for successful builds, not failing builds. However, they are the most useful to us to troubleshoot things when our E2E tests are failing before deploying, therefore we need to be able to access them for failed builds too.
Describe how you'd like this feature to work
Same as for successful builds but for failed builds too.
We can even see in the logs for failed builds that the artifacts are indeed uploaded to your S3 bucket
https://aws-amplify-prod-[region]-artifacts.s3.[region].amazonaws.com/[app_id]/[branch]/000000[build_number]/BUILD/artifacts.zip
, so it's not like they were not existing at all.The text was updated successfully, but these errors were encountered: