refactor: bad sgid session returns 400 instead of 500 #890
KishenKumarrrrrnon-serverless-deploy.yml
on: push
Deploy frontend to AWS Amplify
/
deploy-frontend
4m 0s
Escape commit message to send in slack
0s
Deploy backend to AWS Elastic Beanstalk
/
set_environment
0s
Deploy worker to AWS Elastic Container Service
/
set_environment
0s
Deploy backend to AWS Elastic Beanstalk
/
lint-test
3m 39s
Deploy worker to AWS Elastic Container Service
/
lint
1m 8s
Deploy backend to AWS Elastic Beanstalk
/
build_application
2m 37s
Deploy worker to AWS Elastic Container Service
/
build_application
2m 35s
Deploy backend to AWS Elastic Beanstalk
/
deploy_backend
7m 20s
Deploy backend to AWS Elastic Beanstalk
/
deploy_callback
7m 50s
Deploy worker to AWS Elastic Container Service
/
deploy_sending
11m 53s
Deploy worker to AWS Elastic Container Service
/
deploy_logging
3m 59s
revert-on-e2e-failure
4s
Send Slack message about failed build and tag engineers if it's prod
4s
Send Slack message about successful build
0s
Annotations
1 error and 41 warnings
|
End-to-end Test / playwright-run
Process completed with exit code 1.
|
|
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 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 backend to AWS Elastic Beanstalk / lint-test:
backend/src/core/services/auth.service.ts#L377
Forbidden non-null assertion
|
|
Deploy backend to AWS Elastic Beanstalk / lint-test:
backend/src/govsg/services/govsg.service.ts#L112
Forbidden non-null assertion
|
|
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 worker to AWS Elastic Container Service / build_application
Your docker password is not masked. See https://github.com/aws-actions/amazon-ecr-login#docker-credentials for more information.
|
|
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 backend to AWS Elastic Beanstalk / 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 / build_application
Your docker password is not masked. See https://github.com/aws-actions/amazon-ecr-login#docker-credentials for more information.
|
|
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.
|
|
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: aws-actions/configure-aws-credentials@v2, einaregilsson/beanstalk-deploy@v21. 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 / deploy_backend
Environment update finished, but health is Red and health status is Degraded. Giving it 480 seconds to recover...
|
|
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Environment still has health: Red and health status Degraded. Waiting 459 more seconds before failing...
|
|
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Environment still has health: Red and health status Degraded. Waiting 438 more seconds before failing...
|
|
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Environment still has health: Red and health status Degraded. Waiting 417 more seconds before failing...
|
|
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: aws-actions/configure-aws-credentials@v2, einaregilsson/beanstalk-deploy@v21. 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 / deploy_callback
Environment update finished, but health is Red and health status is Degraded. Giving it 480 seconds to recover...
|
|
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Red and health status Degraded. Waiting 459 more seconds before failing...
|
|
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Red and health status Degraded. Waiting 438 more seconds before failing...
|
|
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Red and health status Degraded. Waiting 417 more seconds before failing...
|
|
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Red and health status Degraded. Waiting 397 more seconds before failing...
|
|
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Red and health status Degraded. Waiting 376 more seconds before failing...
|
|
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.
|
|
End-to-end Test / playwright-run
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
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/.
|
|
Send Slack message about failed build and tag engineers if it's prod
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/.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
playwright-report
Expired
|
408 KB |
|