Hi, I've been using Jenkins for a few years now and we've had great luck getting it to do just about everything we need. We have a number of locks in the system that we use to keep certain scarce resources (mostly GUI for testing) from being used by more than one build at a time.
Recently, we've started using a multi-configuration projection for a multi-os test runner. It was simple to configure and worked great with our main product in the test queue. Basically, we initiate a job with an axis of the test platforms and they all run concurrently, significantly reducing the time to complete. The problem is that we need to add some other builds that will run against the same GUI test farm and must not run simultaneously. Because of the way that our tests are set up, it we need to make sure that a second test on the same OS does not run simultaneously with another. Right now, we're looking to be able to do one of the following: - Lock a resource (named, and based on the axis in a multi-configuration project) immediately before the test run to provide the finest-grained locking for the resources we test with. or - Lock all resources at the beginning of the MC Project and just live with the fact that we can't run multiple MC tests with these resources simultaneously. Either of these cases would work for us, with the former being preferred, but the latter being reasonable. Unfortunately, at this point, we can't find a way to do either of these. Using locks & Latches, it appears that we can only apply a list of pre-defined locks to every single instance of the MC Project, which means for us that we'd be single-threading all of our tests. Is there a technique that I missed that would allow us to do either of these? Thanks, -Gaige -- 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. For more options, visit https://groups.google.com/groups/opt_out.
