-
-
Notifications
You must be signed in to change notification settings - Fork 369
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
Docker Windows Agent #4274
Comments
Yes you right, perhaps we can add "C:" as a prefix to the bind mount if the agent is of the windows/xxx type? |
I would say if workflow workspace has C:\ prefix we do add it there too ... ... feel free to create a pull |
Hmm also if labels platform has windows ... but in any case this is an heuristic and should be an own function checkRunOnWindowsHeuristics(...) bool -> there is no 100% pervect solution :/ |
Do you have an source of your windows git clone plugin ... it's an open issue for our plugin ... |
Yes in the same repo https://github.com/GECO-IT/woodpecker-windows/tree/main/plugins/plugin-git |
We just dockerize the official plugin under windows |
@cduchenoy can you open PRs in the corresponding repos? Thanks for your work! |
the biggest problem we currently have is: no agent running on windows with docker+windows backend ... ... so we might have a look if we can autoscale windows vms on demand via https://github.com/woodpecker-ci/autoscaler |
-> woodpecker-ci/autoscaler#133 to only deploy agent with windows if needed based on lable another option would be if somebody sponsor an agent that run all the time ... but i would call that an hotfix |
Hi, I updated our repository https://github.com/GECO-IT/woodpecker-windows As expected, I submitted our teams-notify plugin :) I would also like to prepare the expected PRs but I don't really know what to send... I just uploaded the docker file for the agent and plugin? |
Component
agent
Describe the bug
From version > 2.6.1 bind mount workspace failed
Steps to reproduce
Expected behavior
No response
System Info
Additional context
First of all: Thank you very much for this useful tool!
For a client we ported the containers (agent, plugin-git) and added one base-step (with chocolatey installed) to Microsoft Windows.
For more information, see https://github.com/GECO-IT/woodpecker-windows
We encounter 2 problems:
1 From agent version > 2.6.0, we have a problem mounting volumes in plugins.
Before this release, we could work around the docker error by adding
We believe this error comes from PR #3933.
2 With the trustedClonePlugins variable https://github.com/woodpecker-ci/woodpecker/blob/main/shared/constant/constant.go
We need to retag our local plugin-git image: “woodpeckerci/plugin-git” to keep netrc secure!
Do you think you could include Windows images officially?
For information: we have also include an installer for local backend on Windows.
Best regards
Cyril DUCHENOY
Geco-iT
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: