• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Deployments
    • None
    • 1
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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.

            [BAM-26130] Queue Multiple Deployments for a Single Environment

            SET Analytics Bot made changes -
            Support reference count New: 1
            Alexey Chystoprudov made changes -
            Status Original: Gathering Interest [ 11772 ] New: Not Being Considered [ 11776 ]

            Alexey Chystoprudov added a comment - - edited

            Environments were designed as shared resources which can't be concurrently updated and have only one version assigned at a moment of time.

            If you use environment as set of procedures/scripts to upload binaries then look at moving that logic to manual build stage. To avoid complexity with maintaining of configuration consider use of Bamboo Specs to manage it. Then you can have one object "APK upload" as single entity at your code which can be used for different plans

            Alexey Chystoprudov added a comment - - edited Environments were designed as shared resources which can't be concurrently updated and have only one version assigned at a moment of time. If you use environment as set of procedures/scripts to upload binaries then look at moving that logic to manual build stage. To avoid complexity with maintaining of configuration consider use of Bamboo Specs to manage it. Then you can have one object "APK upload" as single entity at your code which can be used for different plans
            Santhosh Thokur Raghava created issue -

              Unassigned Unassigned
              562af27be96e Santhosh Thokur Raghava
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: