Fix: allow single CC/BCC recipient to be sent via form-data (#2286) #943
jia1non-serverless-deploy.yml
on: push
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 frontend to AWS Amplify
/
deploy-frontend
5m 57s
Deploy backend to AWS Elastic Beanstalk
/
lint-test
3m 43s
Deploy worker to AWS Elastic Container Service
/
lint
1m 5s
Deploy backend to AWS Elastic Beanstalk
/
build_application
2m 7s
Deploy worker to AWS Elastic Container Service
/
build_application
44s
Deploy backend to AWS Elastic Beanstalk
/
deploy_backend
11m 56s
Deploy backend to AWS Elastic Beanstalk
/
deploy_callback
12m 35s
Deploy worker to AWS Elastic Container Service
/
deploy_sending
5m 3s
Deploy worker to AWS Elastic Container Service
/
deploy_logging
3m 25s
Send Slack message about failed build and tag engineers if it's prod
2s
Send Slack message about successful build
0s
Annotations
1 error and 40 warnings
|
End-to-end Test / playwright-run
Process completed with exit code 1.
|
|
Send slack message when deployment starts
The following actions use a deprecated Node.js version and will be forced to run on node20: slackapi/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Deploy worker to AWS Elastic Container Service / lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Deploy worker to AWS Elastic Container Service / build_application
The following actions use a deprecated Node.js version and will be forced to run on node20: 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 info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
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 backend to AWS Elastic Beanstalk / lint-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
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 / deploy_logging
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
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 frontend to AWS Amplify / deploy-frontend
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, aws-actions/configure-aws-credentials@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Deploy backend to AWS Elastic Beanstalk / build_application
The following actions use a deprecated Node.js version and will be forced to run on node20: 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 info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
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_sending
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
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 backend to AWS Elastic Beanstalk / deploy_backend
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2, einaregilsson/beanstalk-deploy@v21. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
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 407 more seconds before failing...
|
|
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Environment still has health: Red and health status Degraded. Waiting 376 more seconds before failing...
|
|
Deploy backend to AWS Elastic Beanstalk / deploy_callback
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2, einaregilsson/beanstalk-deploy@v21. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
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: Yellow and health status Warning. Waiting 408 more seconds before failing...
|
|
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Yellow and health status Warning. Waiting 377 more seconds before failing...
|
|
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Red and health status Degraded. Waiting 346 more seconds before failing...
|
|
End-to-end Test / playwright-run
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Send Slack message about failed build and tag engineers if it's prod
The following actions use a deprecated Node.js version and will be forced to run on node20: slackapi/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
playwright-report
|
174 KB |
|