Understanding repository partitioning
- Dernière mise à jour2024/10/03
Understanding repository partitioning
A repository is one of the core components that enable you to manage your automation workspace (automations and files). Partitioning helps you scale your repositories and optimize the performance of repository-related operations such as check-in and check-out.
Overview
The Automation 360 repository is a single Git repository where all the bots, forms, processes, and dependency files are stored. As the repository is based on Git, some out-of-the-box version control features are available such as check-in, check-out, version history, roll back, and version compare. Therefore, integrating with an external remote Git is not a requirement in Automation 360.
All the files in the Git repository in Automation 360 are stored for versioning. Over a period of time, the Git repository might become large due to the number of files, size of files, Git commits, and so on. This might lead to latency in the execution of repository actions.
With repository partitioning, you can split the Automation 360 repository folder into separate Git repositories. You can partition the large-sized public repository at the root level folder into multiple Git repositories at selected folder levels, thereby limiting any performance issues in the repository partitions.
Benefits
Some of the benefits of partitioning your repositories include:
- Faster operations due to quick check-in and check-out
- As the folders are partitioned, each partitioned folder has a comparatively smaller number of check-in activities (commits). As a result of these smaller commits, check-in and check-out operations (including concurrent check-ins and check-outs) are quicker.
- Logical segregation of folders in Git space
- Creating multiple repositories in Git mitigates the risk of a single point of failure. Issues in one repository do not adversely impact other repositories or automations contained within them.