Both install-netbird-server (VPS-1) and install-netbird-proxy (proxy-1) apply the netbird-proxy-watchdog role, but neither deploy pipeline's path filter watched ansible/roles/netbird-proxy-watchdog/** — so #153 didn't auto-deploy and had to be triggered manually. Adds the role to both filters.
Note: this PR touches the .woodpecker/deploy-netbird-*.yml files (already in each pipeline's filter), so merging it will itself trigger both deploys — an idempotent re-run that also confirms the auto-deploy path now works.
Both `install-netbird-server` (VPS-1) and `install-netbird-proxy` (proxy-1) apply the `netbird-proxy-watchdog` role, but neither deploy pipeline's path filter watched `ansible/roles/netbird-proxy-watchdog/**` — so #153 didn't auto-deploy and had to be triggered manually. Adds the role to both filters.
Note: this PR touches the `.woodpecker/deploy-netbird-*.yml` files (already in each pipeline's filter), so merging it will itself trigger both deploys — an idempotent re-run that also confirms the auto-deploy path now works.
Both install-netbird-server.yml (VPS-1) and install-netbird-proxy.yml (proxy-1)
apply the netbird-proxy-watchdog role, but neither deploy pipeline's path filter
watched ansible/roles/netbird-proxy-watchdog/**. So the flood-watchdog (#153)
did not auto-deploy on merge and had to be triggered manually. Add the role to
both filters so future watchdog changes redeploy both hosts on merge.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Both
install-netbird-server(VPS-1) andinstall-netbird-proxy(proxy-1) apply thenetbird-proxy-watchdogrole, but neither deploy pipeline's path filter watchedansible/roles/netbird-proxy-watchdog/**— so #153 didn't auto-deploy and had to be triggered manually. Adds the role to both filters.Note: this PR touches the
.woodpecker/deploy-netbird-*.ymlfiles (already in each pipeline's filter), so merging it will itself trigger both deploys — an idempotent re-run that also confirms the auto-deploy path now works.