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

Allow the clone dir path to be configurable

    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

      Hi There,

      I was surprised to find out that pipelines clones the repo to /opt/atlassian/pipelines/agent/build and does not allow customization of this path.
      Pipelines allows us to use custom docker images (which is awesome BTW) which could contain all kinds of different environments, so why would there be an assumption that the user wants to clone the repo to the above location?

      In my particular case, I am trying to replicate a developers machine where the repo is typically cloned somewhere in their home directory with the folder named the same as the repo (as opposed to build).

      In the short term, I was able to work around this using a symlink:
      ln -s "$PWD" /desired/path

      I've come across a few other posts of people desiring this functionality as well [1], [2]

      Attachments

        Activity

          People

            Unassigned Unassigned
            f33c4462b41e ian_colwell
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: