Skip to main content

Bootstrap Build Retry

Synopsis​

Intended end result: Recover from ACR bootstrap build failures caused by branch or lockfile drift.

How this page gets you there: Apply a focused hotfix branch and force a fresh deployment script execution with updated bootstrap inputs.

If the ACR bootstrap build is failing because the build context or UI lockfile is out of sync, create a short-lived fix branch and redeploy against it.

cd /your_local_directory_structure/Alert.CA.CONDOR

git checkout -b hotfix/acr-bootstrap-node-lock
git add server/Dockerfile server/ui/package-lock.json
git commit -m "Fix ACR bootstrap build: sync UI lockfile and use Node 22.16 in server image"
git push -u origin hotfix/acr-bootstrap-node-lock

Then rerun the subscription deployment and force the deployment script to refresh:

cd azure/infrastructure

az deployment sub create \
--name main \
--location westus2 \
--template-file main.bicep \
--parameters parameters.bicepparam \
--parameters bootstrapRepoBranch="hotfix/acr-bootstrap-node-lock" \
bootstrapTimestamp="$(date +%s)"