| Amila Gunathilake your reply describes individual repositories under a directory named "TownSuite". If you're using individual repositories under the TownSuite directory, then you must choose option number 1 that I offered, place the definition of the reference repository in each Jenkinsfile for that repository. In that case, the reference repository is not defined in the organization folder at all, since it is defined in each of the individual repositories and is specific for each repository. I think that is the easiest to manage and the most direct way to provide a reference repository for those repositories that benefit most from it, while allowing you to choose to not use a reference repository for small repositories or infrequently modified repositories. The second option that I offered requires work from the administrator to create a single git repository on the agent. That single git repository combines the content of all relevant repositories into a single repository. The process for creating that single git repository is described in the documentation that I linked in my earlier description of that option. If there is a single git repository that combines the history of all the git repositories, then that single git repository could be referenced in the definition of the organization folder. Most people do not want the complexity of managing that single git repository which combines the history of all git repositories. They typically choose to place the definition of the location of the reference repository in the individual repositories as a part of the checkout step in the Jenkinsfile. |
