Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-14085

Using "AWS CodeDeploy for Bitbucket" addon users can not able to add N number of AWS Deploy applications

    XMLWordPrintable

Details

    • 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.

    Description

      https://aws.amazon.com/blogs/apn/announcing-atlassian-bitbucket-support-for-aws-codedeploy/

      As per the above link, I can able to deploy from multiple branches to multiple servers. But everytime I need to go to codedeploy settings & need to adjust settings.

      Need to implement like under code deploy settings user can able to add "N" number of AWS Deploy Applications

      Assume: There are 2 Applications in aws code deploy say 1. cicd_prod_app, 2. cicd_preprod_app.

      So in bitbucket under settings It has show Application name, S3 bucket name, Branch with addmore option. So user can add his another application, another s3bucket and another branch. Like wise can able to add N number of applications along with S3buckets & branch name.

      In bitbucket Im using multiple branches like production, preproduction, testing, staging etc..
      So when code is pushed to preproduction branch the application cicd_preprod_app need to be trigger & deploy the code to my preprod server. similarly to production.

      or

      After merging code to any branch, When user manually click on Deploy to AWS link, It has to show a radio button with list of applications which we configured under settings.
      so the user will select his appropriate application & Deployment Group and will click on submit

      Thanks & Regards,
      Sandeep Vanam

      Attachments

        Activity

          People

            Unassigned Unassigned
            37cf1a49bd37 sandeep_compassites
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: