Create a QA candidate release #201
GPaolonihrm-qa-release.yml
on: workflow_dispatch
Matrix: build-and-deploy-lambdas
build-and-deploy-service
/
Build Docker Image and Set regions
2m 36s
Matrix: build-and-deploy-service / Deploy to Amazon ECS
generate-pre-release
14s
Annotations
1 error and 45 warnings
|
generate-pre-release
The repository "techmatters/hrm" has no tags matching "v1.19.0-qa*"
|
|
build-and-deploy-lambdas (hrm-domain/lambdas/search-index-consumer) / Build Lambda Image
Process "docker run" closed with code 125
|
|
build-and-deploy-lambdas (resources-domain/lambdas/import-producer) / Deploy to Amazon ECS (us-east-1)
The following actions uses node12 which is deprecated and will be forced to run on node16: marvinpinto/action-inject-ssm-secrets@latest. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build-and-deploy-lambdas (resources-domain/lambdas/import-producer) / Deploy to Amazon ECS (us-east-1)
The following actions use a deprecated Node.js version and will be forced to run on node20: marvinpinto/action-inject-ssm-secrets@latest, aws-actions/configure-aws-credentials@v2, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build-and-deploy-lambdas (resources-domain/lambdas/import-consumer) / Deploy to Amazon ECS (us-east-1)
The following actions uses node12 which is deprecated and will be forced to run on node16: marvinpinto/action-inject-ssm-secrets@latest. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build-and-deploy-lambdas (resources-domain/lambdas/import-consumer) / Deploy to Amazon ECS (us-east-1)
The following actions use a deprecated Node.js version and will be forced to run on node20: marvinpinto/action-inject-ssm-secrets@latest, aws-actions/configure-aws-credentials@v2, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build-and-deploy-lambdas (resources-domain/lambdas/search-index) / Deploy to Amazon ECS (us-east-1)
The following actions uses node12 which is deprecated and will be forced to run on node16: marvinpinto/action-inject-ssm-secrets@latest. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build-and-deploy-lambdas (resources-domain/lambdas/search-index) / Deploy to Amazon ECS (us-east-1)
The following actions use a deprecated Node.js version and will be forced to run on node20: marvinpinto/action-inject-ssm-secrets@latest, aws-actions/configure-aws-credentials@v2, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build-and-deploy-lambdas (hrm-domain/lambdas/contact-retrieve-transcript) / Deploy to Amazon ECS (us-east-1)
The following actions uses node12 which is deprecated and will be forced to run on node16: marvinpinto/action-inject-ssm-secrets@latest. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build-and-deploy-lambdas (hrm-domain/lambdas/contact-retrieve-transcript) / Deploy to Amazon ECS (us-east-1)
The following actions use a deprecated Node.js version and will be forced to run on node20: marvinpinto/action-inject-ssm-secrets@latest, aws-actions/configure-aws-credentials@v2, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build-and-deploy-lambdas (hrm-domain/lambdas/files-urls) / Deploy to Amazon ECS (us-east-1)
The following actions uses node12 which is deprecated and will be forced to run on node16: marvinpinto/action-inject-ssm-secrets@latest. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build-and-deploy-lambdas (hrm-domain/lambdas/files-urls) / Deploy to Amazon ECS (us-east-1)
The following actions use a deprecated Node.js version and will be forced to run on node20: marvinpinto/action-inject-ssm-secrets@latest, aws-actions/configure-aws-credentials@v2, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build-and-deploy-lambdas (hrm-domain/lambdas/search-index-consumer) / Deploy to Amazon ECS (us-east-1)
The following actions uses node12 which is deprecated and will be forced to run on node16: marvinpinto/action-inject-ssm-secrets@latest. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build-and-deploy-lambdas (hrm-domain/lambdas/search-index-consumer) / Deploy to Amazon ECS (us-east-1)
The following actions use a deprecated Node.js version and will be forced to run on node20: marvinpinto/action-inject-ssm-secrets@latest, aws-actions/configure-aws-credentials@v2, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build-and-deploy-lambdas (lambdas/job-complete) / Deploy to Amazon ECS (us-east-1)
The following actions uses node12 which is deprecated and will be forced to run on node16: marvinpinto/action-inject-ssm-secrets@latest. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build-and-deploy-lambdas (lambdas/job-complete) / Deploy to Amazon ECS (us-east-1)
The following actions use a deprecated Node.js version and will be forced to run on node20: marvinpinto/action-inject-ssm-secrets@latest, aws-actions/configure-aws-credentials@v2, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build-and-deploy-service / Build Docker Image and Set regions
Process "docker run" closed with code 125
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
The following actions uses node12 which is deprecated and will be forced to run on node16: marvinpinto/action-inject-ssm-secrets@latest. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
The following actions use a deprecated Node.js version and will be forced to run on node20: marvinpinto/action-inject-ssm-secrets@latest, aws-actions/configure-aws-credentials@v2, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
build-and-deploy-service / Deploy to Amazon ECS (us-east-1)
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.
|
|
generate-pre-release
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
generate-pre-release
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
generate-pre-release
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
generate-pre-release
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
generate-pre-release
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1, marvinpinto/[email protected], marvinpinto/action-inject-ssm-secrets@latest, slackapi/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
generate-pre-release
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v1, marvinpinto/[email protected], aws-actions/configure-aws-credentials@v2, marvinpinto/action-inject-ssm-secrets@latest, 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 | |
|---|---|---|
|
techmatters~hrm~A3AX4Z.dockerbuild
|
43.1 KB |
|
|
techmatters~hrm~NVS9R3.dockerbuild
|
45.5 KB |
|
|
techmatters~hrm~PDQEP4.dockerbuild
|
36.8 KB |
|
|
techmatters~hrm~Q1AE1V.dockerbuild
|
37.8 KB |
|
|
techmatters~hrm~XP3AT9.dockerbuild
|
38.7 KB |
|
|
techmatters~hrm~ZF5RTH.dockerbuild
|
38.1 KB |
|
|
test-artifacts
|
198 KB |
|
|
workflow-scripts-artifacts
|
1.12 KB |
|