Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-2552

Provide a way to locate the repository directory on disk

    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      When you create a repository the directory it is created in is a number.

      I created three repositories, then I ssh'd into my server to add hooks to them. It was confusing to figure out which repository what in which folder.

            [BSERV-2552] Provide a way to locate the repository directory on disk

            William Crighton [CCC] added a comment - - edited

            added to provide reference reason for linking to my feature request STASH-3208

            My thought - if Stash provided a rest call to query repositories based on ID then the FEDS plugin could be modified to use the directory name in a rest call to pull Repository intel out of Stash - that way the Crucible Repo it then creates could have a meaningful name. And there would be other uses for such a rest call as listed in this ticket.

            William Crighton [CCC] added a comment - - edited added to provide reference reason for linking to my feature request STASH-3208 My thought - if Stash provided a rest call to query repositories based on ID then the FEDS plugin could be modified to use the directory name in a rest call to pull Repository intel out of Stash - that way the Crucible Repo it then creates could have a meaningful name. And there would be other uses for such a rest call as listed in this ticket.

            gmellema - is the plugin listed above not sufficient for your needs?

            Which other tools do you need to use with the Git repositories? If we can understand your use cases then it will help us deliver a better solution for you.

            Seb Ruiz (Inactive) added a comment - gmellema - is the plugin listed above not sufficient for your needs? Which other tools do you need to use with the Git repositories? If we can understand your use cases then it will help us deliver a better solution for you.

            For my company this is a showstopper for using Stash. Key requirement is that we can use the GIT repo with different tools. We therefore need some meaningfull names i.s.o. ID's.
            Please let me know when this is solved, so we can reconsider a purchase.

            Gert-Jan Mellema added a comment - For my company this is a showstopper for using Stash. Key requirement is that we can use the GIT repo with different tools. We therefore need some meaningfull names i.s.o. ID's. Please let me know when this is solved, so we can reconsider a purchase.

            The problem with using names is that we could get into interesting problems with various characters on viarious file systems.

            Anton, now Stash (2.0.2) allow only [A-Z0-9_] for project key and only [A-Za-z0-9_\-\.] for repository name, nothing anymore characters. All this symbols are crossplatformed already

            Alexey Efimov added a comment - The problem with using names is that we could get into interesting problems with various characters on viarious file systems. Anton, now Stash (2.0.2) allow only [A-Z0-9_] for project key and only [A-Za-z0-9_\-\.] for repository name, nothing anymore characters. All this symbols are crossplatformed already

            Adrián added a comment -

            I just need to know where is the Git repo, since I am connecting Stash with a git-svn synchronizer.

            From the description seems that James needs the same info in order in order to install some hooks.

            Adrián added a comment - I just need to know where is the Git repo, since I am connecting Stash with a git-svn synchronizer. From the description seems that James needs the same info in order in order to install some hooks.

            jhinch (Atlassian) added a comment - - edited

            Hi Adrian,

            The SysInfo Plugin is now a supported (but not bundled plugin). That means we will continue to ensure it works with new versions of Stash. It hopefully will not be required to be updated every release. The APIs it is using have now stablised.

            It would be good to get feedback as to what extra functionality in your opinion would be required in order for this issue to be resolved. One thing which comes to mind is providing this information via REST.

            jhinch (Atlassian) added a comment - - edited Hi Adrian, The SysInfo Plugin is now a supported (but not bundled plugin). That means we will continue to ensure it works with new versions of Stash. It hopefully will not be required to be updated every release. The APIs it is using have now stablised. It would be good to get feedback as to what extra functionality in your opinion would be required in order for this issue to be resolved. One thing which comes to mind is providing this information via REST.

            Adrián added a comment -

            hi kmarchenko, the plugin was presented by jhinch as a workaround and not as a solution.

            Will the plugin be updated every time you release a new Stash version? Why don't you reopen this and close it when there is a solution actually shipped with the product?

            Adrián added a comment - hi kmarchenko , the plugin was presented by jhinch as a workaround and not as a solution. Will the plugin be updated every time you release a new Stash version? Why don't you reopen this and close it when there is a solution actually shipped with the product?

            Closing this issue. Solution is Repository System Info Plugin https://marketplace.atlassian.com/plugins/com.atlassian.stash.plugin.repository-sysinfo-plugin

            Kostya Marchenko (Inactive) added a comment - Closing this issue. Solution is Repository System Info Plugin https://marketplace.atlassian.com/plugins/com.atlassian.stash.plugin.repository-sysinfo-plugin

            jhinch (Atlassian) added a comment - - edited

            To help mitigate this issue we've created a plugin for Stash, the Repository System Info Plugin. This will show the path to the repository on disk in the UI (only accessible to System Administrators). It is available as a separate download for Stash 1.2+

            jhinch (Atlassian) added a comment - - edited To help mitigate this issue we've created a plugin for Stash, the Repository System Info Plugin . This will show the path to the repository on disk in the UI (only accessible to System Administrators). It is available as a separate download for Stash 1.2+

            Daniel R added a comment - - edited

            Daniel R added a comment - - edited A temporary workaround can be found here: https://confluence.atlassian.com/display/STASHKB/Identifying+a+Repository+on+the+Stash+Server

              Unassigned Unassigned
              17a6326b25ae James Murray
              Votes:
              6 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: