Release / fix: attribute some errors as client errors (#294) #34
event_release.yml
on: push
Paths Filter
4s
Matrix: Release / Release / publish
CD
/
...
/
Health Check - staging
2s
CD
/
...
/
Deployment Tests - staging
1m 34s
CD
/
...
/
Swift Integration Tests - staging
1m 13s
CD
/
...
/
health-check
CD
/
...
/
validate-rust
CD
/
...
/
validate-swift
Annotations
2 errors and 10 warnings
CD / Validate Staging / Swift Integration Tests - staging
❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration)
|
CD / Validate Staging / Deployment Tests - staging
Process completed with exit code 101.
|
Release / Release / Update Version
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/
|
CD / Staging / Deploy App / Deploy App `staging`
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.
|
CD / Staging / Deploy App / Deploy App `staging`
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.
|
CD / Staging / Deploy App / Deploy App `staging`
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.
|
CD / Staging / Deploy App / Deploy App `staging`
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.
|
CD / Staging / Deploy App / Deploy App `staging`
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.
|
CD / Staging / Deploy App / Deploy App `staging`
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.
|
CD / Staging / Deploy App / Deploy App `staging`
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.
|
CD / Staging / Deploy App / Deploy App `staging`
Environment URL '' is not a valid http(s) URL, so it will not be shown as a link in the workflow graph.
|
CD / Validate Staging / Swift Integration Tests - staging
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
notify-tests test_results
Expired
|
274 KB |
|