Skip to content

Replaces Empty Favicon with Trento Logo (#3144) #13309

Replaces Empty Favicon with Trento Logo (#3144)

Replaces Empty Favicon with Trento Logo (#3144) #13309

Triggered via push November 15, 2024 09:27
Status Success
Total duration 19m 1s
Artifacts 2

ci.yaml

on: push
Matrix: elixir-deps
Npm dependencies
29s
Npm dependencies
Npm E2E dependencies
20s
Npm E2E dependencies
Rebuild target branch dependencies
4m 19s
Rebuild target branch dependencies
Check if the integration test criteria are met, store in the job output
0s
Check if the integration test criteria are met, store in the job output
Check if the regression test criteria are met, store in the job output
0s
Check if the regression test criteria are met, store in the job output
Check common misspellings
22s
Check common misspellings
Generate project documentation
52s
Generate project documentation
Static Code Analysis
4m 37s
Static Code Analysis
Chromatic deployment
2m 46s
Chromatic deployment
Matrix: API bc check
Matrix: Integration tests
Matrix: Regression tests
Build the docker image for the demo environment
9m 2s
Build the docker image for the demo environment
Build and push container images
4m 35s
Build and push container images
Commit to OBS to generate container image
2m 5s
Commit to OBS to generate container image
Commit to OBS to generate RPM package
1m 18s
Commit to OBS to generate RPM package
Deploy updated images to the demo environment
1m 1s
Deploy updated images to the demo environment
Use photofinish to push mock data to the demo environment
2m 26s
Use photofinish to push mock data to the demo environment
Fit to window
Zoom out
Zoom in

Annotations

1 error and 32 warnings
Deploy updated images to the demo environment
Process completed with exit code 1.
Generate project documentation
The following actions uses node12 which is deprecated and will be forced to run on node16: lee-dohm/generate-elixir-docs@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Generate project documentation
The following actions use a deprecated Node.js version and will be forced to run on node20: lee-dohm/generate-elixir-docs@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Generate project documentation
documentation references type "Trento.Users.User.t()" but it is hidden or private
Generate project documentation
documentation references type "Trento.Users.User.t()" but it is hidden or private
Rebuild target branch dependencies
use Bitwise is deprecated. import Bitwise instead
Rebuild target branch dependencies
Jason.decode!/1 is undefined (module Jason is not available or is yet to be defined)
Rebuild target branch dependencies
Logger.warn/1 is deprecated. Use Logger.warning/2 instead
Rebuild target branch dependencies
Application.get_env/3 is discouraged in the module body, use Application.compile_env/3 instead
Rebuild target branch dependencies
Logger.warn/1 is deprecated. Use Logger.warning/2 instead
Rebuild target branch dependencies
variable "email" is unused (if the variable is not meant to be used, prefix it with an underscore)
Rebuild target branch dependencies
Plug.Adapters.Cowboy.child_spec/4 is deprecated. Use Plug.Cowboy.child_spec/4 instead
Rebuild target branch dependencies
Plug.Adapters.Cowboy.http/3 is deprecated. Use Plug.Cowboy.http/3 instead
Rebuild target branch dependencies
Logger.warn/1 is deprecated. Use Logger.warning/2 instead
Legacy key/value format with whitespace separator should not be used: Dockerfile#L3
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L23
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L34
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L2
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L22
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L24
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L35
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L4
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Commit to OBS to generate container image
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/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L3
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L4
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L24
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L34
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L2
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L22
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L23
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L35
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Artifacts

Produced during runtime
Name Size
trento-project~web~S5UPTE.dockerbuild
99.4 KB
trento-project~web~X9SM18.dockerbuild
81.2 KB