Skip to content

Add MySQL topology server implementation #1

Add MySQL topology server implementation

Add MySQL topology server implementation #1

Triggered via pull request March 12, 2026 00:26
Status Success
Total duration 24m 56s
Artifacts 2

docker_ci.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

18 warnings
Docker Test Cluster
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/bake-action@5be5f02ff8819ecd3092ea6b2e6261c31774f2b4, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36, step-security/harden-runner@e3f713f2d8f53843e71c69a996d56f51aa9adfb9. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Legacy key/value format with whitespace separator should not be used: docker/bootstrap/Dockerfile.common#L28
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: docker/bootstrap/Dockerfile.common#L27
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: docker/bootstrap/Dockerfile.common#L26
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: docker/bootstrap/Dockerfile.common#L25
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: docker/bootstrap/Dockerfile.common#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/
FROM --platform flag should not use a constant value: docker/bootstrap/Dockerfile.common#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64" More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
FROM --platform flag should not use a constant value: docker/bootstrap/Dockerfile.common#L4
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64" More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
Default value for global ARG results in an empty or invalid base image name: docker/bootstrap/Dockerfile.common#L4
InvalidDefaultArgInFrom: Default value for ARG "${image}" results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Java Docker Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/bake-action@5be5f02ff8819ecd3092ea6b2e6261c31774f2b4, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36, step-security/harden-runner@e3f713f2d8f53843e71c69a996d56f51aa9adfb9. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Legacy key/value format with whitespace separator should not be used: docker/bootstrap/Dockerfile.common#L28
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: docker/bootstrap/Dockerfile.common#L27
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: docker/bootstrap/Dockerfile.common#L26
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: docker/bootstrap/Dockerfile.common#L25
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: docker/bootstrap/Dockerfile.common#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/
FROM --platform flag should not use a constant value: docker/bootstrap/Dockerfile.common#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64" More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
FROM --platform flag should not use a constant value: docker/bootstrap/Dockerfile.common#L4
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64" More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
Default value for global ARG results in an empty or invalid base image name: docker/bootstrap/Dockerfile.common#L4
InvalidDefaultArgInFrom: Default value for ARG "${image}" results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/

Artifacts

Produced during runtime
Name Size Digest
block~vitess~CO8QEU+1.dockerbuild
200 KB
sha256:a9dc1744987628bc1e717bcba0b206c714db23a540ca49df231796e841c1811f
block~vitess~PHPBHY+1.dockerbuild
169 KB
sha256:f1be26441644a375b46fe4442f8f2d760cf3e64be4345695c4ee1bc3105b515d