ci: distinguish between missing secrets and variables in QA build
SonarQube Analysis / sonarqube (pull_request) Canceled after 24s
Tests / backend-integration (pull_request) Canceled after 0s
Tests / frontend-e2e (pull_request) Canceled after 0s
Tests / backend-unit (pull_request) Canceled after 5s

Separate error messages and guidance for missing secrets versus variables in the QA build configuration check to improve clarity for developers.
This commit is contained in:
2026-08-18 08:20:43 -05:00
parent b3bf42b859
commit c350f0a588
+11 -4
View File
@@ -39,13 +39,20 @@ jobs:
run: |
missing=""
[ -n "${{ secrets.REGISTRY_TOKEN }}" ] || missing="$missing REGISTRY_TOKEN"
[ -n "${{ vars.REGISTRY_USER }}" ] || missing="$missing REGISTRY_USER"
[ -n "${{ secrets.BREVO_API_KEY }}" ] || missing="$missing BREVO_API_KEY"
missingVars=""
[ -n "${{ vars.REGISTRY_USER }}" ] || missing="$missing REGISTRY_USER"
[ -n "${{ vars.QA_NOTIFY_TO }}" ] || missing="$missing QA_NOTIFY_TO"
[ -n "${{ vars.QA_NOTIFY_FROM }}" ] || missing="$missing QA_NOTIFY_FROM"
if [ -n "$missing" ]; then
echo "::error::Missing configuration:$missing"
echo "Secrets go in Settings > Actions > Secrets; variables in Settings > Actions > Variables."
if [ -n "$missing" || -n "$missingVars" ]; then
if [ -n "$missing" ]; then
echo "::error::Missing configuration secrets:$missing"
echo "Secrets go in Settings > Actions > Secrets"
fi
if [ -n "$missingVars" ]; then
echo "::error::Missing configuration variables:$missingVars"
echo "Variables go in Settings > Actions > Variables."
fi
exit 1
fi
echo "All required secrets and variables are present."