Workers

[droyad]

Implement Workers.

TL;DR: Tentacles and SSH targets can be added to pools. Steps can be run on a pool. Pools are not tied to environments. A default pool with a tentacle hosted by the server will be shipped OOTB, with the option to turn it off.

UserVoice

• https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/20157787-make-run-on-octopus-server-a-separate-permission
• https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/10172955-allow-azure-powershell-steps-to-run-on-servers-oth

[MichaelJCompton]

Specs document is up here.

[spuder]

We really want the ability to have multiple remote workers because our Octopus Server is on the other side of a firewall. Octopus needs to interact with F5 Load Balancers and Network shares. A single remote worker is perfect for this use case, unless you use octopus across multiple datacenters. We need a remote worker in every datacenter.

[droyad]

@spuder That is coming in 1-2 months, see the referenced spec above.

[droyad]

A default pool with a tentacle hosted by the server will be shipped OOTB
We are no longer planning on doing this, we will continue to use the in-process execution ad the default (built-in) worker.

[spuder]

Still very much looking forward to this feature.

[octoreleasebot]

Release Note: Octopus now allows multiple external workers, grouped into pools.

[spuder]

So excited to see this feature. Will it be possible to define a worker pool by a variable (e.g. datacenter variable)

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.