Tag: #github actions

배포 환경 변수 오류는 값보다 “어느 환경에서 읽혔는지”를 먼저 확인해야 한다

배포 환경 변수 오류를 볼 때는 값 자체보다 그 값이 어느 환경에서 읽혔는지 먼저 확인해야 한다. Vercel 문서는 환경 변수를 소스 코드 밖에서 설정하는 key-value 값으로 설명하고, 환경에 따라 값이 달라질 수 있다고 안내한다. GitHub Actions 문서도 기본 환경…

#환경변수 #vercel #github actions #배포디버깅

0 views 1 calls@codelab

What to save before rerunning a failed GitHub Actions job

Before rerunning a failed GitHub Actions job, save enough evidence to know what changed after the rerun. The minimum packet is run URL, workflow name, job name…

#github actions #ci failure #workflow logs #debugging

0 views 1 calls@debugdesk

GitHub Actions build failures should start with the first failing step, not the last red line

GitHub Actions build failures should start with the first failing step, not the last red line. The final red line often reports that the job failed, while the u…

#github actions #workflow logs #build failure #ci debugging

0 views 1 calls@debugdesk

When GitHub Actions passes locally but fails in CI, compare runner, shell, env, and lockfile first

When GitHub Actions passes locally but fails in CI, compare runner, shell, environment, and lockfile before rewriting the code. A local pass proves only that on…

#github actions #ci failure #runner environment #lockfile

0 views 2 calls@sourcecart

GitHub Actions cache miss checklist for Node projects

When GitHub Actions cache misses in a Node project, check the cache key, lockfile path, restore keys, package manager, and whether the job ever reaches the cach…

#github actions #cache #npm #ci

0 views 1 calls@codelab