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

Allow to omit redirection feature when renaming a repostiory

XMLWordPrintable

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

      This one is directly related to ----BSERV-3751 and also to https://jira.atlassian.com/browse/BSERV-10293

      Previously the feature "Allow historical aliasing of projects and repositories" has been integrated, which from my perspective is breaking Bitbucket for previous users that rely on the fact that the old URL are not valid anymore, which was and is the expected behaviour. This change changes this default behaviour and in our case causing troubles. From my point of view this has to be configurable either globally or on renaming a repository by providing a checkbox "Alias to old repo?". In both cases the default doesn't matter as long it is a choice, but I'd vote to default to the old behaviour.

          Form Name

            [BSERV-10230] Allow to omit redirection feature when renaming a repostiory

            Michael Pfister added a comment -

            So, as my support request #SSP-25879 and Jira Ticket BSERV-10293 has been closed by @Imran Khan, when can we expect a patch for this issue?
            It's not that this issue affects me in my personal work but as I decided to buy this product and we're spending several thousands of dollars into the Atlassian suite I'm the one having to justify for the computing delays and crashes this "expected behavior" caused in our server centers.

            As written before, just saying this is now the expected behavior doesn't fix the issue this change causes for CI driven systems. This may be a nice little change for people using the repo but when you have several hundred computing nodes getting configurations from Bitbucket automatically, this change causes some serious issues as described further in my support request.

            In other words, the current behavior is not acceptable for CI driven systems.

            Michael Pfister added a comment - So, as my support request  #SSP-25879 and Jira Ticket  BSERV-10293  has been closed by @Imran Khan, when can we expect a patch for this issue? It's not that this issue affects me in my personal work but as I decided to buy this product and we're spending several thousands of dollars into the Atlassian suite I'm the one having to justify for the computing delays and crashes this "expected behavior" caused in our server centers. As written before, just saying this is now the expected behavior doesn't fix the issue this change causes for CI driven systems. This may be a nice little change for people using the repo but when you have several hundred computing nodes getting configurations from Bitbucket automatically, this change causes some serious issues as described further in my support request. In other words, the current behavior is not acceptable for CI driven systems.

            Michael Rolli added a comment - - edited

            Hi Imran

            I know that since solving BSERV-3751 this redirection feature is now implemented. And no, we did not expect this when we upgraded and then were puzzled, why old URLs still work though they should not. This is the harmless case. Now consider that you unawarely rely on this redirection on some system and months later some opens a new repo using the old name of the other and suddenly all system relying on the setup redirection not only stop to work but also get wrong data.

            From my side, this feature might be beneficial for a lot of users - and yeah, github.com has it, well then it must be good, but...

            My point is, that this was not the default behavior before in Bitbucket and you silently changed the default behavior. This is dangerous. In most cases, we (University of Bern - paying customer) don't want this redirection and now we are not able to avoid this as it is NOT CONFIGURABLE!

            So, my feature request is:

            • As a Bitbucket user I want to avoid setting up redirection URLs on moving a repo by clicking a checkbox "Do not setup redirects". The checkbox' default is dependent on the setting-wide default (see next point).
            • The systemwide default for setting up redirects on moving a repo can be left to true as it is now, but as a Bitbucket administrator I want to to be able to change this system-wide in the system settings.

            I hope you now get my point. Thanks.

            Michael Rolli added a comment - - edited Hi Imran I know that since solving BSERV-3751 this redirection feature is now implemented. And no, we did not expect this when we upgraded and then were puzzled, why old URLs still work though they should not. This is the harmless case. Now consider that you unawarely rely on this redirection on some system and months later some opens a new repo using the old name of the other and suddenly all system relying on the setup redirection not only stop to work but also get wrong data. From my side, this feature might be beneficial for a lot of users - and yeah, github.com has it, well then it must be good, but... My point is, that this was not the default behavior before in Bitbucket and you silently changed the default behavior. This is dangerous. In most cases, we (University of Bern - paying customer) don't want this redirection and now we are not able to avoid this as it is NOT CONFIGURABLE! So, my feature request is: As a Bitbucket user I want to avoid setting up redirection URLs on moving a repo by clicking a checkbox "Do not setup redirects". The checkbox' default is dependent on the setting-wide default (see next point). The systemwide default for setting up redirects on moving a repo can be left to true as it is now, but as a Bitbucket administrator I want to to be able to change this system-wide in the system settings. I hope you now get my point. Thanks.

            Imran Khan added a comment -

            Hi michael.rolli

            Thanks for your suggestion. This is the expected behavior now and we don't have any plans to change it in short term. I would open this issue so that other users can vote/watch it.

            Imran Khan added a comment - Hi michael.rolli Thanks for your suggestion. This is the expected behavior now and we don't have any plans to change it in short term. I would open this issue so that other users can vote/watch it.

              Unassigned Unassigned
              a432f47e72f0 Michael Rolli
              Votes:
              14 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated: