On Fri, Jan 16, 2015 at 6:35 AM, Rob Mandeville < rmandevi...@dekaresearch.com> wrote:
> The beauty of Jenkins is that a single installation can run on multiple > hosts. That’s what slave nodes are for. Rather than cross-compiling, just > put together a Linux machine with GCC, and build your Linux binaries > there. Here’s what you do. > > > > First off, I’m assuming that you have a job like “Build windows binary”. > Configure that job, and check the “Restrict where this project can be run” > box so that it runs on “master”. This forces it to run on the Jenkins > server itself; since your Jenkins server runs in Windows, this forces this > job to run on a Windows machine. > That's the type of setup I use, and it works very well. I've also liked using the Platform Labeler plugin so that labels are automatically assigned to the slave for operating system name, operating system version, and chip architecture. I also found a case where the Implied Labels plugin was a great help. Mark Waite -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFbkueuKquHOM4bZsft5RkSqswyRfknWPCXJyS4WYDb%2Bw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
