Hello, I'm working with a legacy system which is using Jenkins for automated testing, and attempting to upgrade and modernize it.
The issue is, that it is a large cross platform project. Where a job usually must have at least two nodes at the same time: one big Linux node and one smaller windows node. For example: start a simulator/emulator on windows, and then start the rest of the software on Linux. In production, the simulator/emulator is replaced with a physical machine. Currently, the solution has been to set up the Linux nodes as usual Jenkins slaves, and then manually map each executor node to a windows VM... The pool of Windows machines aren't known by Jenkins. The current situation is and has been working. But you can imagine this doesn't scale dynamically, which is a requirement for the future. There are some jobs which do not require both a Linux and Windows pair, so while those are run it would be nice to have the pairs not so statically bound to each other. Work has begun to containerize and port everything to Linux, but in the meantime are there other Jenkins users who have similar requirements? Thanks, Alexander Moriarty -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ca01f9ed-073b-4682-a0d8-85b607e5d717%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
