Skip to content
CI

deploy-demo #12661

Sign in to view logs

deploy-demo

deploy-demo #12661

Triggered via repository dispatch September 27, 2024 08:04
@stefanotorresistefanotorresi
deploy-demo ⁠ 0b8ad99
Status Success
Total duration 17m 7s
Artifacts 1

ci.yaml

on: repository_dispatch
Matrix: elixir-deps
Npm dependencies
23s
Npm dependencies
Npm E2E dependencies
23s
Npm E2E dependencies
Rebuild target branch dependencies
4m 15s
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
38s
Check common misspellings
Generate project documentation
0s
Generate project documentation
Test
1m 53s
Test
Static Code Analysis
4m 53s
Static Code Analysis
Run FE tests
1m 58s
Run FE tests
Chromatic deployment
0s
Chromatic deployment
End to end tests
13m 44s
End to end tests
Matrix: API bc check
Matrix: Integration tests
Matrix: Regression tests
Build the docker image for the demo environment
4m 25s
Build the docker image for the demo environment
Build and push container images
0s
Build and push container images
Commit to OBS to generate container image
0s
Commit to OBS to generate container image
Commit to OBS to generate RPM package
1m 26s
Commit to OBS to generate RPM package
Deploy updated images to the demo environment
52s
Deploy updated images to the demo environment
Use photofinish to push mock data to the demo environment
1m 33s
Use photofinish to push mock data to the demo environment
Fit to window
Zoom out
Zoom in

Annotations

1 error and 18 warnings
Deploy updated images to the demo environment
Process completed with exit code 1.
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#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#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#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#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~MTII7T.dockerbuild Expired
75.2 KB