Support running generic-worker via worker-runner on windows
Categories
(Taskcluster :: Workers, enhancement)
Tracking
(Not tracked)
People
(Reporter: dustin, Assigned: dustin)
References
Details
This will involve some work with windows services.
|
Assignee | |
Comment 1•5 years ago
|
||
I tried to get nssm to talk to named pipes, but it didn't work for bidirectional connections -- I think it connects multiple times for stdin and stdout and stderr. So, I added a short option to generic-worker to explicitly connect to a pipe:
|
|
Assignee | |
Comment 2•5 years ago
|
||
https://github.com/taskcluster/taskcluster-worker-runner/pull/79 is ready for review now, too.
Note that neither of these patches fully support the worker-runner protocol just yet -- generic-worker still implicitly supports an empty set of features. Even the empty set of features, however, gets us a setup where worker-runner and generic-worker logging are in the same stream. We can add that support to generic-worker in a followup.
|
|
Assignee | |
Comment 3•5 years ago
|
||
Those are both merged, and this will be out in the next version of tc-worker-runner (which I think will be 1.0.0 since it is now usable for all of our supported workers) and the next version of generic-worker.
|
||
Comment 4•5 years ago
|
||
Released in generic-worker 16.6.0.
Description
•