Skip to content
Pull request environment

Add sap hana scale up cost optimized and performance optimized discovery #7281

Sign in to view logs

Add sap hana scale up cost optimized and performance optimized discovery

Add sap hana scale up cost optimized and performance optimized discovery #7281

Triggered via pull request November 27, 2024 13:57
@EMaksyEMaksy
synchronize #3152
hana_cost_optimized
Status Success
Total duration 10m 23s
Artifacts 1

pr_env.yaml

on: pull_request
Check if the environment creation criteria are met, store in the job output
0s
Check if the environment creation criteria are met, store in the job output
Build and push pull request container image
4m 38s
Build and push pull request container image
Create or update the pr environment
3m 23s
Create or update the pr environment
Use photofinish to push mock data to the pr environment
1m 53s
Use photofinish to push mock data to the pr environment
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
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#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#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#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#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#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#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/

Artifacts

Produced during runtime
Name Size
trento-project~web~SFL9ZA.dockerbuild
71.7 KB