Skip to content

chore: add mock for new endpoint #879

chore: add mock for new endpoint

chore: add mock for new endpoint #879

Triggered via push February 8, 2024 07:49
Status Cancelled
Total duration 5m 59s
Artifacts
Deploy frontend to AWS Amplify  /  deploy-frontend
4m 3s
Deploy frontend to AWS Amplify / deploy-frontend
Escape commit message to send in slack
0s
Escape commit message to send in slack
Deploy backend to AWS Elastic Beanstalk  /  set_environment
0s
Deploy backend to AWS Elastic Beanstalk / set_environment
Deploy worker to AWS Elastic Container Service  /  set_environment
0s
Deploy worker to AWS Elastic Container Service / set_environment
Deploy backend to AWS Elastic Beanstalk  /  lint-test
3m 4s
Deploy backend to AWS Elastic Beanstalk / lint-test
Deploy worker to AWS Elastic Container Service  /  lint
1m 7s
Deploy worker to AWS Elastic Container Service / lint
Send slack message when deployment starts
2s
Send slack message when deployment starts
Deploy backend to AWS Elastic Beanstalk  /  build_application
0s
Deploy backend to AWS Elastic Beanstalk / build_application
Deploy worker to AWS Elastic Container Service  /  build_application
45s
Deploy worker to AWS Elastic Container Service / build_application
Deploy backend to AWS Elastic Beanstalk  /  deploy_backend
0s
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Deploy backend to AWS Elastic Beanstalk  /  deploy_callback
0s
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Deploy worker to AWS Elastic Container Service  /  deploy_sending
2m 42s
Deploy worker to AWS Elastic Container Service / deploy_sending
Deploy worker to AWS Elastic Container Service  /  deploy_logging
2m 44s
Deploy worker to AWS Elastic Container Service / deploy_logging
End-to-end Test  /  set_environment
End-to-end Test / set_environment
End-to-end Test  /  playwright-run
End-to-end Test / playwright-run
revert-on-e2e-failure
6s
revert-on-e2e-failure
Send Slack message about failed build and tag engineers if it's prod
0s
Send Slack message about failed build and tag engineers if it's prod
Send Slack message about successful build
0s
Send Slack message about successful build
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 24 warnings
Deploy backend to AWS Elastic Beanstalk / lint-test
Process completed with exit code 1.
Deploy worker to AWS Elastic Container Service / deploy_sending
The operation was canceled.
Deploy worker to AWS Elastic Container Service / deploy_logging
The operation was canceled.
Send slack message when deployment starts
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: slackapi/slack-github-action@v1.23.0. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy worker to AWS Elastic Container Service / lint
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy worker to AWS Elastic Container Service / build_application
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, aws-actions/configure-aws-credentials@v2, aws-actions/amazon-ecr-login@v1, docker/setup-buildx-action@v2, docker/build-push-action@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy backend to AWS Elastic Beanstalk / lint-test
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy frontend to AWS Amplify / deploy-frontend
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, aws-actions/configure-aws-credentials@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy worker to AWS Elastic Container Service / deploy_sending
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: aws-actions/configure-aws-credentials@v2, aws-actions/amazon-ecs-render-task-definition@v1, aws-actions/amazon-ecs-deploy-task-definition@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'compatibilities' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'taskDefinitionArn' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'requiresAttributes' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'revision' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'status' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'registeredAt' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'registeredBy' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: aws-actions/configure-aws-credentials@v2, aws-actions/amazon-ecs-render-task-definition@v1, aws-actions/amazon-ecs-deploy-task-definition@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'compatibilities' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'taskDefinitionArn' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'requiresAttributes' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'revision' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'status' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'registeredAt' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'registeredBy' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
revert-on-e2e-failure
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: aws-actions/configure-aws-credentials@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.