Hello, One of the things we use Jenkins for is as a launcher for our deployment processes. As all our different services an environments have an identical build process, we've implemented this as one parameterized job called "deploy", with parameters "product" and "environment" (production, staging, validation, etc.). Our Jenkins system is pretty heavily used, so we concurrent jobs.
What I'd like is to be able to set something up such that there can only be one active build of the "deploy" job with a certain set of parameters, but that builds with other parameters aren't blocked. In concrete terms, if there's a "deploy" build with product=mail and environment=production in process, any other "deploy" builds with those values of product and environment should stay enqueued, but a "deploy" build with product=mail and environment=staging should be able to be executed (in parallel with the other one). Do you have any suggestions for ways to accomplish this with the existing Jenkins plugins? I know I could just make distinct jobs (eg. deploy-mail-production and deploy-mail-staging) and use Build Blocker, but this will add a bunch of overhead, and change the usability experience for my customers/engineers in a way that I'm not excited about. Any advice would be appreciated. Thanks, Dan -- 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/c9d5143d-3e87-44ca-a12c-bcdbb44339d2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
