fix: ui bug (#2236) #866
non-serverless-deploy.yml
on: push
Deploy frontend to AWS Amplify
/
deploy-frontend
4m 15s
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 34s
Deploy worker to AWS Elastic Container Service
/
lint
1m 5s
Deploy backend to AWS Elastic Beanstalk
/
build_application
35s
Deploy worker to AWS Elastic Container Service
/
build_application
46s
Deploy backend to AWS Elastic Beanstalk
/
deploy_backend
11m 6s
Deploy backend to AWS Elastic Beanstalk
/
deploy_callback
12m 2s
Deploy worker to AWS Elastic Container Service
/
deploy_sending
3m 58s
Deploy worker to AWS Elastic Container Service
/
deploy_logging
3m 56s
revert-on-e2e-failure
12s
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 27 warnings
End-to-end Test / playwright-run
Process completed with exit code 1.
|
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:
backend/src/govsg/services/govsg.service.ts#L112
Forbidden non-null assertion
|
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
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 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
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 458 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_backend
Environment still has health: Red and health status Degraded. Waiting 396 more seconds before failing...
|
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Environment still has health: Red and health status Degraded. Waiting 375 more seconds before failing...
|
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 428 more seconds before failing...
|
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Environment still has health: Red and health status Degraded. Waiting 396 more seconds before failing...
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
playwright-report
Expired
|
7.59 MB |
|