Improve Bitbucket Server integration for teams with large number of project/repositories
ideally... gearset should not be hitting https://adlm.nielsen.com/bitbucket/rest/api/1.0/repos
first. It should hit https://adlm.nielsen.com/bitbucket/rest/api/1.0/projects to get a list of projects
then allow the end user to select the project
then https://adlm.nielsen.com/bitbucket/rest/api/1.0/projects/{projectKey}/repos to get a list of repos on the project the end user selects
Noel Austin
shared this idea
Gearset will now filter by project first when selecting a repo/branch for Bitbucket Server
-
Shubham Jain
commented
Agreed!! if this is implemented then we can deploy sandbox refresh Project stories and other Project stories too.
-
Animesh Deshpande
commented
Yes agree, will help a lot.
-
Noel Austin
commented
We are unable to configure Gearset CI jobs against our BitBucket branches because of this issue. Our BitBucket server has over 1000 repositories which exceeds the Gearset limit. Having the option to filter by project would allow us to move forward with our BitBucket integration.
-
Gleb Urobushkin
commented
I agree, it should be fairly straightforward to implement and quickly improve user experience.