Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Triggering a PR deployment on a multi server app creates an unwanted deployment on 2nd server #1871

Closed
baptisteArno opened this issue Mar 20, 2024 · 1 comment · Fixed by #1893

Comments

@baptisteArno
Copy link

Description

Whenever I deploy a PR on an application that has 2 servers, it deploys the PR correctly (and without errors) on primary server but then there is also a deployments triggered for 2nd server:

CleanShot 2024-03-20 at 10 25 39

The logs of that deployment start with:

[2024-Mar-20 09:25:13.472740] Found a suitable build server (build).
[2024-Mar-20 09:25:13.474680] Starting deployment of baptisteArno/typebot.io:main to chat-api-2.
[2024-Mar-20 09:25:13.937055] Preparing container with helper image: ghcr.io/coollabsio/coolify-helper:latest.

Which is clearly something I don't want when triggering a PR deployment

Minimal Reproduction (if possible, example repository)

baptisteArno/typebot.io#1200

Exception or Error

No response

Version

v4.0.0-beta.239

@andrasbacsai
Copy link
Member

This will be fixed in the upcoming version.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants