CI/CD

Automatize atualizações de tarefas e relatórios nos seus pipelines.

Autenticação

export GITSCRUM_ACCESS_TOKEN="seu-token"

Armazene o token nos segredos da sua plataforma CI.

GitHub Actions

name: Deploy
on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      
      - name: Instalar GitScrum CLI
        run: curl -fsSL https://cli.gitscrum.com/install.sh | sh
      
      - name: Deploy
        run: ./deploy.sh
      
      - name: Atualizar tarefa
        run: |
          TASK_ID=$(git log -1 --format=%s | grep -oE 'GS-[0-9]+' | head -1)
          if [ -n "$TASK_ID" ]; then
            gitscrum task update $TASK_ID --status deployed
          fi
        env:
          GITSCRUM_ACCESS_TOKEN: ${{ secrets.GITSCRUM_ACCESS_TOKEN }}

GitLab CI

atualizar-gitscrum:
  stage: notify
  script:
    - curl -fsSL https://cli.gitscrum.com/install.sh | sh
    - TASK_ID=$(echo $CI_COMMIT_MESSAGE | grep -oE 'GS-[0-9]+' | head -1)
    - |
      if [ -n "$TASK_ID" ]; then
        gitscrum task update $TASK_ID --status deployed
      fi
  variables:
    GITSCRUM_ACCESS_TOKEN: $GITSCRUM_ACCESS_TOKEN

Bitbucket Pipelines

pipelines:
  branches:
    main:
      - step:
          name: Atualizar GitScrum
          script:
            - curl -fsSL https://cli.gitscrum.com/install.sh | sh
            - TASK_ID=$(git log -1 --format=%s | grep -oE 'GS-[0-9]+' | head -1)
            - gitscrum task update $TASK_ID --status deployed

Melhores Práticas

1. Armazene tokens como segredos
2. Não imprima tokens em logs
3. Cache o CLI para builds mais rápidos