|
| 1 | +# Tell seabird-nix that this repo moved, so it can bump the matching flake |
| 2 | +# input. seabird-nix names its inputs <repo>-dev and <repo>-release, so |
| 3 | +# CI_REPO_NAME is the only repo-specific piece and this file is identical in |
| 4 | +# every service repo — copy it as-is. |
| 5 | +# |
| 6 | +# This calls the CLI directly rather than using woodpeckerci/plugin-trigger: |
| 7 | +# that plugin can only restart the target repo's last pipeline (inheriting |
| 8 | +# its original event) or fire a deployment, and neither is what's wanted |
| 9 | +# here. `pipeline create` makes a genuinely new manual pipeline, which keeps |
| 10 | +# deployment events meaning only "an actual deploy-rs run". |
| 11 | +steps: |
| 12 | + - name: trigger-dev-bump |
| 13 | + image: woodpeckerci/woodpecker-cli:v3.17-alpine |
| 14 | + environment: |
| 15 | + WOODPECKER_SERVER: ${CI_SYSTEM_URL} |
| 16 | + WOODPECKER_TOKEN: |
| 17 | + from_secret: seabird_bot_woodpecker_token |
| 18 | + commands: |
| 19 | + - | |
| 20 | + woodpecker-cli pipeline create seabird-chat/seabird-nix \ |
| 21 | + --branch main \ |
| 22 | + --var SEABIRD_CI_TASK=nix-input-bump \ |
| 23 | + --var INPUT_NAME=${CI_REPO_NAME}-dev |
| 24 | + when: |
| 25 | + - event: push |
| 26 | + branch: main |
| 27 | + |
| 28 | + - name: trigger-release-bump |
| 29 | + image: woodpeckerci/woodpecker-cli:v3.17-alpine |
| 30 | + environment: |
| 31 | + WOODPECKER_SERVER: ${CI_SYSTEM_URL} |
| 32 | + WOODPECKER_TOKEN: |
| 33 | + from_secret: seabird_bot_woodpecker_token |
| 34 | + commands: |
| 35 | + - | |
| 36 | + woodpecker-cli pipeline create seabird-chat/seabird-nix \ |
| 37 | + --branch main \ |
| 38 | + --var SEABIRD_CI_TASK=nix-input-bump \ |
| 39 | + --var INPUT_NAME=${CI_REPO_NAME}-release |
| 40 | + when: |
| 41 | + - event: push |
| 42 | + branch: release |
0 commit comments