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

Ability to restrict who can run deployment builds in Pipelines

    XMLWordPrintable

    Details

    • Feedback Policy:

      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

      When pipelines are deploying to production or have access to other important resources, customers want to either prevent changes to configuration or restrict the ability to run the pipeline to certain members of their team.

      This is related to BCLOUD-12844, and needs further discussion with customers before we settle on a solution.

      Original suggestion

      Pipelines should only read from bitbucket-pipelines.yml that is in the main branch and run branch-specific tasks from that file as well. That way developers that do not or should not have access to the build file can be blocked from the main branch but still be able to push to other branches (which still runs the branch-specific build code defined in the bitbucket-pipelines.yml file in the main branch). bitbucket-pipelines.yml files in non-main branches should be ignored and, obviously, should not be required to be in the branch that is defining the branch-specific build code.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            gkoh Gideon Koh (Inactive)
            Votes:
            49 Vote for this issue
            Watchers:
            67 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: