-
Notifications
You must be signed in to change notification settings - Fork 45
[EE] No machine type on new pipeline #187
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
Comments
2 tasks
dexyk
added a commit
that referenced
this issue
Apr 1, 2025
## 📝 Description **Fixes** #187 This PR introduces the following improvements: - Sets the default machine type to the first available self-hosted agent type. - Sets the default container image for promotions that use Docker environments. ### Behavior - **Self-hosted agent default:** When adding a promotion with a block (without overriding global agent definition), the first available self-hosted agent is selected by default.  - **Docker environment default:** When adding a promotion with a block that uses a Docker environment, the default container image is automatically set.  ## ✅ Checklist - [x] I have tested this change - [x] ~This change requires documentation update~ - N/A
skipi
pushed a commit
that referenced
this issue
Apr 14, 2025
## 📝 Description **Fixes** #187 This PR introduces the following improvements: - Sets the default machine type to the first available self-hosted agent type. - Sets the default container image for promotions that use Docker environments. ### Behavior - **Self-hosted agent default:** When adding a promotion with a block (without overriding global agent definition), the first available self-hosted agent is selected by default.  - **Docker environment default:** When adding a promotion with a block that uses a Docker environment, the default container image is automatically set.  ## ✅ Checklist - [x] I have tested this change - [x] ~This change requires documentation update~ - N/A
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Creating a new pipeline in Workflow builder results in the empty
machine type
parameter, in turn making the pipeline invalid.As an alternative solution, on the self-hosted versions of Semaphore, when new pipeline is created the machine type should be set to the first available machine, and environment to Docker fixed values.
So it would look something like:
Steps to reproduce
Additional context
The text was updated successfully, but these errors were encountered: