This is the first of a series of blogposts regarding Polarion ALM.
Polarion allows you to have everything – Polarion data (workitems, documents, wiki pages, …) + work artifacts (souce, binaries, documentation, ..) – in one repo, or to separate work artifacts from Polarion data. This feature is called „external repo“.
I strongly recommend external repo because:
- Polarion repo stays small: your work artifacts might explode in pure size and number of revisions.
- Usage of hooks is simplified: you might implement hooks to eg. enforce coding rules. Never apply hooks to Polarion data (unless you really, really know what you’re doing)
- Performance improves: size, hooks will slow down Polarion.
- Transfer of Projects for Investigation, tests etc. will ease: for testing new Polarion release you only need Polarion data.
- External repo can be Git: your developers might love git