HI Team,
We are part of Admin team and we are at the version Digitial.AI Release v23.1.0 and we have Bitbucket plugin installed in our instance. This plugin gives an option to clone the repository from the Bitbucket. If any user clones the repository in using the Digital.AI Release it may clone the repository on our servers and this will consume the space on our servers.
To avoid this we need an enhancement on the Bitbucket plugin to remove the clone repository task method.
Thank you,
Purushotham
by: Purushotham R. | about a year ago | Integrations
Comments
Purushotham, in the Release environment, you have the ability to control task visibility for users. To achieve this, Release administrators can navigate to Users and Permissions -> Task Access -> locate Bitbucket Server -> and disable the "Clone Repository" task. By following these steps, the Clone Repository task will be hidden for all users.
Alternatively, if the above solution is not viable, consider providing a mount path in the Local Path field of the Clone Repository task. This path should point to the location where teams store their cloned repositories. Implement a scheduled job, such as a cron job, to regularly purge or archive folders and paths on the server. This approach ensures that repository removal from Release does not impact teams using specific cloned repositories as part of their Release processes.
If this does not address your specific requirements, could you please provide an example of your use case to better understand your needs?
Similar request on the subject: https://ideas.digital.ai/devops/Idea/Detail/4119
We do not have plans to implement this change in the BitBucket plugin as this is a very specific to customer infrastructure implementation. The clean up can be achieved using the scripted task. If you need any help on this, please reach out to your Sales Engineer.