Compare commits

..

14 Commits

Author SHA1 Message Date
0a6852acbb Merge PR #8: fix(ci): Cloud Build com --gcs-source-staging-dir + --async + poll loop
All checks were successful
CD / build (push) Successful in 5m47s
2026-05-07 16:27:47 +00:00
037a3f4d93 fix(ci): troca --suppress-logs por --async + poll loop
All checks were successful
CD / build (pull_request) Successful in 4m3s
--suppress-logs nessa versão do gcloud CLI no runner ainda tenta ler
logs no fim e dá exit != 0 quando a SA não tem Viewer no projeto. Build
real do PR #8 deu SUCCESS (image lab-18 em AR), mas a step falhou na
finalização do gcloud.

Com --async, gcloud retorna o build ID logo após enfileirar e sai.
Poll explícito via builds describe (que usa cloudbuild.builds.get,
já em builds.editor). Mata o build no primeiro estado terminal != SUCCESS.
2026-05-07 13:20:27 -03:00
18c22e85c4 fix(ci): --gcs-source-staging-dir + --suppress-logs no builds submit
Some checks failed
CD / build (pull_request) Failing after 5m27s
Quota_project sozinho não resolve. Reproduzi local com a SA gitea-cd e
peguei a HTTP 403 raw da Storage API: dois calls bloqueados em sequência:

1. GET /storage/v1/b/_cloudbuild → resolvido com grant de roles/storage.admin
   no bucket (storage.buckets.get vinha do projectEditor legacy ACL, que
   gitea-cd não é).

2. GET /storage/v1/b?prefix=_cloudbuild&project=corepetro → 403 em
   storage.buckets.list. Esse permission é project-scoped (não dá pra
   grantar bucket-scoped). Em vez de inflar a SA com storage.admin no
   projeto, --gcs-source-staging-dir explícito faz gcloud pular o
   auto-detect inteiro e usar o bucket especificado.

E --suppress-logs evita o stream que exige Viewer/Owner no projeto pra
ler Cloud Logging — gitea-cd não tem; o build ainda é aguardado e o
exit code propaga correto.

Validado: build de teste alpine deu SUCCESS na primeira tentativa com
esses dois flags.
2026-05-07 12:02:36 -03:00
154d498699 fix(ci): seta quota_project pro gcloud builds submit não 500 em service usage
Some checks failed
CD / build (pull_request) Failing after 40s
`gcloud builds submit` faz uma chamada interna à Service Usage API antes
de uploadar o source pro bucket _cloudbuild. Quando autentica via SA key
(google-github-actions/auth), o credentials file não tem quota_project, e
gcloud cai num default que não é corepetro — a chamada à SU falha com
"serviceusage.services.use forbidden" mesmo com roles/serviceusage.serviceUsageConsumer
concedida no projeto.

Fix: setar billing/quota_project explícito antes do builds submit + env
var CLOUDSDK_BILLING_QUOTA_PROJECT como cinto-suspensório.
2026-05-07 10:57:50 -03:00
1352edf289 ci: retrigger after granting storage.objectAdmin on _cloudbuild bucket
Some checks failed
CD / build (push) Failing after 44s
2026-05-07 10:54:36 -03:00
0bae06d411 Merge PR #7: fix(ci): volta build pra Cloud Build + bump Node 20
Some checks failed
CD / build (push) Failing after 43s
2026-05-07 13:37:41 +00:00
23828ee5ef fix(ci): volta build pra Cloud Build + bump Node 20 no webcomponent
Some checks failed
CD / build (pull_request) Failing after 41s
- Reverte cd.yml pra Cloud Build (gcloud builds submit). Kaniko da PR #5
  quebra porque a imagem kaniko:debug não tem /bin/sleep no PATH e o
  act-runner usa entrypoint=["/bin/sleep","10800"] no container do job.
- Bump node:18 -> node:20 no stage do webcomponent (Vite >= 5 exige Node 20+).

Pré-requisito pro Cloud Build funcionar: SA gitea-cd precisa de
roles/cloudbuild.builds.editor + roles/serviceusage.serviceUsageConsumer.
2026-05-07 10:21:18 -03:00
f72f0fec94 Merge pull request 'fix: troca header markdown por negrito na saudação inicial' (#6) from fix/welcome-message-bold into main
Some checks failed
CD / build (push) Failing after 3s
CD / deploy (push) Has been skipped
Reviewed-on: #6
2026-05-07 12:01:35 +00:00
736cc0f277 fix: troca header markdown por negrito na saudação inicial
Some checks failed
CD / build (pull_request) Failing after 1s
CD / deploy (pull_request) Has been skipped
O `####` aparecia literal no balão da saudação porque o markdown
processor do bootstrap renderiza headers, mas o estilo destoava
do resto. Usa **negrito** pra destaque visual consistente.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-06 16:21:48 -03:00
f61b1a05e5 Merge pull request 'fix(ci): build com Kaniko' (#5) from fix/kaniko-build into main
Some checks failed
CD / build (push) Failing after 1s
CD / deploy (push) Has been skipped
2026-05-06 13:19:23 +00:00
9a6c43edfc fix(ci): build com Kaniko (sem Docker daemon, sem Cloud Build, sem IAM novo)
Some checks failed
CD / build (pull_request) Failing after 1s
CD / deploy (pull_request) Has been skipped
Job 1 (build) roda dentro da imagem gcr.io/kaniko-project/executor:debug
e usa _json_key auth do AR. Job 2 (deploy) é runner default + kubectl
e depende do build via 'needs'.
2026-05-06 10:19:19 -03:00
4ea625f95c Merge pull request 'fix(ci): build via Cloud Build (sem docker local)' (#4) from fix/cloud-build into main
Some checks failed
CD / build (push) Failing after 32s
2026-05-06 12:46:05 +00:00
e0e5585d7c fix(ci): build remoto via Cloud Build (sem docker local) + gke auth plugin
Some checks failed
CD / build (pull_request) Failing after 29s
Step container do act-runner não consegue conectar no docker daemon
(dind sidecar usa tcp://localhost:2375 mas o step roda em network
isolada). Cloud Build resolve sem precisar configurar networking do
runner — bonus: build em VM linux/amd64 sem cross-compile.
2026-05-06 09:42:07 -03:00
4de6055040 Merge pull request 'fix(ci): instala docker CLI + kubectl no step' (#3) from fix/install-docker-kubectl into main
Some checks failed
CD / build (push) Failing after 28s
2026-05-06 12:29:37 +00:00
3 changed files with 48 additions and 20 deletions

View File

@ -14,16 +14,17 @@ jobs:
steps: steps:
- uses: actions/checkout@v4 - uses: actions/checkout@v4
# Imagem default do runner (node:18-bullseye) não traz docker CLI nem kubectl — # Instala kubectl + auth plugin (gcloud já vem via setup-gcloud).
# instalamos sob demanda. Eventualmente isso vai pra imagem custom do runner. # Build é feito remoto via Cloud Build (não precisa Docker no runner).
- name: Install docker CLI + kubectl - name: Install kubectl + gke-auth-plugin
run: | run: |
apt-get update -qq apt-get update -qq
apt-get install -y -qq docker.io apt-get install -y -qq apt-transport-https ca-certificates gnupg curl
KVER=$(curl -sL https://dl.k8s.io/release/stable.txt) curl -fsSL https://packages.cloud.google.com/apt/doc/apt-key.gpg | gpg --dearmor -o /usr/share/keyrings/cloud.google.gpg
curl -sL "https://dl.k8s.io/release/${KVER}/bin/linux/amd64/kubectl" -o /usr/local/bin/kubectl echo "deb [signed-by=/usr/share/keyrings/cloud.google.gpg] https://packages.cloud.google.com/apt cloud-sdk main" > /etc/apt/sources.list.d/google-cloud-sdk.list
chmod +x /usr/local/bin/kubectl apt-get update -qq
docker --version && kubectl version --client=true apt-get install -y -qq kubectl google-cloud-cli-gke-gcloud-auth-plugin
kubectl version --client=true
- name: Auth GCP - name: Auth GCP
uses: google-github-actions/auth@v2 uses: google-github-actions/auth@v2
@ -35,21 +36,48 @@ jobs:
with: with:
project_id: ${{ secrets.GCP_PROJECT }} project_id: ${{ secrets.GCP_PROJECT }}
- name: Configure Docker auth - name: Build & push (Cloud Build, sem Docker local)
run: gcloud auth configure-docker ${{ secrets.AR_LOCATION }}-docker.pkg.dev --quiet
- name: Build image
run: | run: |
set -e
IMG="${IMAGE_BASE}/${{ gitea.event.repository.name }}:lab-${{ gitea.run_number }}" IMG="${IMAGE_BASE}/${{ gitea.event.repository.name }}:lab-${{ gitea.run_number }}"
docker build --platform=linux/amd64 -t "$IMG" . # --gcs-source-staging-dir: pula o auto-detect que precisa de
# storage.buckets.list (project-scope). gitea-cd só tem grant
# na bucket _cloudbuild, não no projeto inteiro.
# --async: gcloud retorna assim que o build é enfileirado. Sem
# isso, gcloud tenta streamar Cloud Logging, exige Viewer/Owner
# no projeto, e --suppress-logs nessa versão do CLI ainda dá
# exit != 0 quando não consegue ler. Polling abaixo é o trade.
BUILD_ID=$(gcloud builds submit \
--tag "$IMG" \
--project=${{ secrets.GCP_PROJECT }} \
--timeout=30m \
--gcs-source-staging-dir="gs://${{ secrets.GCP_PROJECT }}_cloudbuild/source" \
--async \
--format="value(id)")
echo "Cloud Build kicked off: $BUILD_ID"
# Poll até terminar. gcloud builds describe usa cloudbuild.builds.get
# (já incluído em roles/cloudbuild.builds.editor).
while true; do
STATUS=$(gcloud builds describe "$BUILD_ID" \
--project=${{ secrets.GCP_PROJECT }} \
--region=global \
--format="value(status)")
echo "[$(date -u +%H:%M:%S)] build $BUILD_ID: $STATUS"
case "$STATUS" in
SUCCESS) break ;;
FAILURE|INTERNAL_ERROR|TIMEOUT|CANCELLED|EXPIRED)
echo "::error::Cloud Build $STATUS — ver console: https://console.cloud.google.com/cloud-build/builds/$BUILD_ID?project=${{ secrets.GCP_PROJECT }}"
exit 1
;;
esac
sleep 15
done
echo "IMG=$IMG" >> $GITHUB_ENV echo "IMG=$IMG" >> $GITHUB_ENV
- name: Push image (apenas em push pra master/main)
if: github.event_name == 'push'
run: docker push "$IMG"
- name: Deploy hml2 (apenas em push pra master/main) - name: Deploy hml2 (apenas em push pra master/main)
if: github.event_name == 'push' if: github.event_name == 'push'
env:
USE_GKE_GCLOUD_AUTH_PLUGIN: "True"
run: | run: |
gcloud container clusters get-credentials ${{ secrets.GKE_CLUSTER }} --region ${{ secrets.GKE_REGION }} --project ${{ secrets.GCP_PROJECT }} gcloud container clusters get-credentials ${{ secrets.GKE_CLUSTER }} --region ${{ secrets.GKE_REGION }} --project ${{ secrets.GCP_PROJECT }}
NS=${{ secrets.K8S_NAMESPACE }} NS=${{ secrets.K8S_NAMESPACE }}
@ -64,7 +92,7 @@ jobs:
if kubectl get deployment "$DEPLOYMENT" -n "$NS" >/dev/null 2>&1; then if kubectl get deployment "$DEPLOYMENT" -n "$NS" >/dev/null 2>&1; then
CONTAINER=$(kubectl get deployment "$DEPLOYMENT" -n "$NS" -o jsonpath='{.spec.template.spec.containers[0].name}') CONTAINER=$(kubectl get deployment "$DEPLOYMENT" -n "$NS" -o jsonpath='{.spec.template.spec.containers[0].name}')
kubectl set image deployment/"$DEPLOYMENT" -n "$NS" "$CONTAINER=$IMG" kubectl set image deployment/"$DEPLOYMENT" -n "$NS" "$CONTAINER=$IMG"
kubectl rollout status deployment/"$DEPLOYMENT" -n "$NS" --timeout=300s kubectl rollout status deployment/"$DEPLOYMENT" -n "$NS" --timeout=600s
else else
echo "Deployment $DEPLOYMENT não existe no ns $NS — pulei set image (provavelmente é o 1º deploy e o kubectl apply acabou de criar)" echo "Deployment $DEPLOYMENT não existe no ns $NS — pulei set image (provavelmente é o 1º deploy e o kubectl apply acabou de criar)"
fi fi

View File

@ -7,7 +7,7 @@ ARG VANNA_UPSTREAM_COMMIT=365d0617c1a4567ffee1b19b40c27feb4206bfcf
# ============================================================================ # ============================================================================
# Stage 1 — webcomponent (Node) # Stage 1 — webcomponent (Node)
# ============================================================================ # ============================================================================
FROM node:18-bookworm-slim AS webcomponent FROM node:20-bookworm-slim AS webcomponent
ARG VANNA_UPSTREAM_COMMIT ARG VANNA_UPSTREAM_COMMIT
RUN apt-get update && apt-get install -y --no-install-recommends git ca-certificates \ RUN apt-get update && apt-get install -y --no-install-recommends git ca-certificates \
&& rm -rf /var/lib/apt/lists/* && rm -rf /var/lib/apt/lists/*

View File

@ -154,7 +154,7 @@ def build_agent(
temperature = float(os.environ.get("OPENAI_TEMPERATURE", "1.0")) temperature = float(os.environ.get("OPENAI_TEMPERATURE", "1.0"))
welcome_message = ( welcome_message = (
"#### 👋 Olá! Aqui é a ClubPetro IA\n\n" "**👋 Olá! Aqui é a ClubPetro IA**\n\n"
"Sua assistente de inteligência de dados. Eu transformo dados complexos em " "Sua assistente de inteligência de dados. Eu transformo dados complexos em "
"respostas claras, direto ao ponto. Precisa de um relatório de faturamento, " "respostas claras, direto ao ponto. Precisa de um relatório de faturamento, "
"entender a performance da sua equipe ou aprofundar no comportamento de " "entender a performance da sua equipe ou aprofundar no comportamento de "