Suggestion

Based on the customer's requirement-

• Assume you have a build plan that produced a binary, such as an .apk, to be published to the Google Play Store.
• These binaries could, in theory, be deployed concurrently as Google's API would allow such a thing.
• The deployment environment is purely designed to deploy these apks, and while concurrency isn't something we need, a queue is.
• When you try to kick off another deployment in an environment that is already running, you get a warning.
• The goal is to have multiple individuals queue these deployments to deploy their individual plan branch artifacts.