Create a QA candidate release #205
GPaolonihrm-qa-release.yml
on: workflow_dispatch
Matrix: build-and-deploy-lambdas
build-and-deploy-service
/
Build Docker Image and Set regions
2m 24s
Matrix: build-and-deploy-service / Deploy to Amazon ECS
generate-pre-release
20s
Annotations
44 warnings
|
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 (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-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 (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 (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/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 (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-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.
|
|
run-e2e-tests
No files were found with the provided path: flex-plugins/e2e-tests/test-results. No artifacts will be uploaded.
|
|
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/action-automatic-releases@v1.2.1, marvinpinto/action-inject-ssm-secrets@latest, slackapi/slack-github-action@v1.14.0. 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/action-automatic-releases@v1.2.1, aws-actions/configure-aws-credentials@v2, marvinpinto/action-inject-ssm-secrets@latest, slackapi/slack-github-action@v1.14.0. 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~1C73BO.dockerbuild
|
38.6 KB |
|
|
techmatters~hrm~3KZMT2.dockerbuild
|
37 KB |
|
|
techmatters~hrm~55H3JM.dockerbuild
|
36.1 KB |
|
|
techmatters~hrm~IESUF9.dockerbuild
|
45.2 KB |
|
|
techmatters~hrm~N00Z1O.dockerbuild
|
38.2 KB |
|
|
techmatters~hrm~O5EPCT.dockerbuild
|
42.7 KB |
|
|
techmatters~hrm~PRO6SF.dockerbuild
|
43 KB |
|
|
techmatters~hrm~Y2088E.dockerbuild
|
26.1 KB |
|
|
workflow-scripts-artifacts
|
1.12 KB |
|