check

GRIF-683: Fixing invalid ascii characters in LCM bricks parameters #346

Job	Run time
prepare-env	47s
gooddata-ruby-fossa-licenses-validate-LR-ticket-zuul	4s
gooddata-ruby-lcm-integration-e2e / LCM-integration-e2e-tests	9m 34s
ready-to-merge	3s
gooddata-ruby-lcm-build-pipeline	0s
prepare-env	47s
gooddata-ruby-lcm-integration-e2e / LCM-integration-e2e-tests	12m 35s
gooddata-ruby-fossa-licenses-validate-LR-ticket-zuul	4s
gooddata-ruby-lcm-build-pipeline / prepare-build	30s
gooddata-ruby-lcm-build-pipeline / dockerfiles-validation (lcm-bricks-nextversion) / dockerfile-validation	28s
gooddata-ruby-lcm-build-pipeline / dockerfiles-validation (lcm-bricks) / dockerfile-validation	25s
gooddata-ruby-lcm-build-pipeline / charts-validation	0s
gooddata-ruby-lcm-build-pipeline / helm-charts-build	0s
gooddata-ruby-lcm-build-pipeline / services-build (lcm-bricks)	15m 17s
gooddata-ruby-lcm-build-pipeline / services-build (lcm-bricks-nextversion)	3m 25s
gooddata-ruby-lcm-build-pipeline / register-bricks-staging	51s
gooddata-ruby-lcm-build-pipeline / build-helmreleases	0s
gooddata-ruby-lcm-build-pipeline / revert-staging-pr	0s
gooddata-ruby-lcm-build-pipeline / create-staging-pr	0s
gooddata-ruby-lcm-build-pipeline / wait-for-deployment	0s
gooddata-ruby-lcm-build-pipeline / promote-to-stable	0s
gooddata-ruby-lcm-build-pipeline / create-manual-merge-prod-pr	0s
gooddata-ruby-lcm-build-pipeline / create-auto-merge-prod-pr	0s
ready-to-merge	3s
gooddata-ruby-lcm-build-pipeline / register-bricks-prod	0s
gooddata-ruby-lcm-build-pipeline / create-comment-with-pr-urls	0s
	44m 53s

Provide feedback