Join GitHub today
Garden-Windows Worker Support #2175
Moving the drain and registration to
Its probably easiest to support this in BOSH first and add support to the binaries later, so lets just focus on the challenges there.
A Modest Proposal
A good first step would be to create a
I think this would be a good start, and implementing resources will still be something to chew on.. It would be less than ideal if we need to create windows containers for every base resource type to support them.
CC + Thanks to @natalieparellano
Supporting base resource types as part of this issue may be a tad ambitious. Some of the major ones like
For now, I've added a
This all works and I've replaced our own Windows worker with the new BOSH jobs. The third-party concourse-windows-worker-release should no longer be necessary.
@vito Well, the Garden Windows team did its part to fulfill the Garden API contract in particular for this feature, so it'd be a shame to see that work fall to the wayside. Pivotal also sees customer demand for this, particularly for building .NET apps. And I'd love to see if this works already, too. What would need to be true to move this forward at least a little bit? cc: @jama-pivotal
@awmartin I've been wanting this for months myself, it's just difficult to justify prioritizing it over all the other things that are sorely needed by our users, Pivotal customers included. :( Right now we have pretty big fish to fry (spaces, large-scale operability, RBAC, Kubernetes runtime).
Honestly we're pretty reliant on the community (which includes Pivotal teams) to contribute to the areas they feel passionate about in any way they can. The scope of this project is huge compared to the size of our team - we can't do everything ourselves. I'm happy to provide guidance there.
The first step would be to take
I'll ping @topherbullock too and see where this could fit in the Runtime backlog (I mainly stick to Core - see https://project.concourse-ci.org/), but I can't promise anything. It'd be faster to just try it out yourself and open an issue/PR for any changes needed. :)
@vito It looks like the strategy you mentioned needs to change as Houdini is directly consumed as part of the Concourse binary now. Concourse also shells out to
I think the approach would be to use the