Skip to content

Use medium-sized instances during high-scale time periods #22656

Use medium-sized instances during high-scale time periods

Use medium-sized instances during high-scale time periods #22656

Triggered via pull request November 19, 2025 17:15
Status Success
Total duration 4m 52s
Artifacts 5

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile#L39
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#L38
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#L61
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#L37
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/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L47
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L6
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L60
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/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L39
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_SECRET_ACCESS_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Default value for global ARG results in an empty or invalid base image name: Dockerfile#L50
InvalidDefaultArgInFrom: Default value for ARG ruby:${RUBY_VERSION}-slim results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L50
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
coverage-report
main is missing merged-coverage.xml. See documentation on how to add this
coverage-report
No artifacts found for the following workspaces: ci,cron

Artifacts

Produced during runtime
Name Size Digest
minitest-coverage
48.6 KB
sha256:965aa779315774ff050d7c6cd2f66e13b503a9642f3501a3731d1d537a5b49b0
minitest-reports
25.9 KB
sha256:cee42a4281184abd2936ce73059226737b540f1a8bd07420c40cf1e84eb558b2
neinteractiveliterature~intercode~NRN98B.dockerbuild
122 KB
sha256:3050692bb9e71a1766601c228faa9753c1a47ee18b425becb251045132a1eab4
vitest-coverage
88.6 KB
sha256:40b08324b0ec5926634710dde0b6a0103504cc600e1d29b4642246c7fd91a710
vitest-reports
538 KB
sha256:c6e50fc6a4b4a549aa64d0c14549898eee21e1ffddbc339d6dec3008be7b62ba