Skip to content

ciを作成

ciを作成 #7

Triggered via pull request October 23, 2024 17:38
@piny940piny940
synchronize #11
ci
Status Success
Total duration 2m 44s
Artifacts 2

stg-deploy.yaml

on: pull_request
stg-build-backend-main
0s
stg-build-backend-main
stg-build-frontend-main
0s
stg-build-frontend-main
stg-build-backend
52s
stg-build-backend
stg-build-frontend
53s
stg-build-frontend
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
piny940
approved Oct 23, 2024
staging and staging

Annotations

6 warnings
Legacy key/value format with whitespace separator should not be used: frontend/Dockerfile#L11
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/
Variables should be defined before their use: frontend/Dockerfile#L31
UndefinedVar: Usage of undefined variable '$BACKEND_HOST' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: frontend/Dockerfile#L31
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: frontend/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/
stg-build-frontend
Unexpected input(s) 'build-args', valid inputs are ['tags', 'github-actor', 'gh-token', 'path']
stg-build-frontend
Unexpected input(s) 'build-args', valid inputs are ['tags', 'github-actor', 'gh-token', 'path']

Artifacts

Produced during runtime
Name Size
piny940~auth~5B0UY4.dockerbuild Expired
50.1 KB
piny940~auth~JMY2VH.dockerbuild Expired
38.4 KB