Tomasz Adamski

@adamdubiel So... I think monorepo itself isn't an issue. I believe that JGit has some performance issues with big repositories (our has ~20k commits in master). I did an example...

this is the whole config we use (so the answer is "default") ``` scmVersion{ tag { prefix = 'appname' } } ```

I've dug into the code a little bit and I have an impression that retrieving `scmVersion.version` (which is all you need in configuration phase) does few more things "by the...

I was in particular concerned about code starting from this point https://github.com/allegro/axion-release-plugin/blob/master/src/main/groovy/pl/allegro/tech/build/axion/release/infrastructure/git/GitRepository.groovy#L204 but after a 2nd look I get that order of tags returned isn't necessarily in the order we...

and the winner is... `performance_tests`. It is slightly faster, instead of ~0.5s for each versioned module, it takes ~0.3s now.

I remember I thought about that initially. Sounds great. Each versioned module has its own configuration with custom tag prefix.

it is not uber important right now ;) have a great vacations!

another thing is that I can spend some spare time on it. Just write few words how you imagine adding cache. Some starting point would be useful!

@adamdubiel we have one project with big list of includes in `settings.gradle`.

Unfortunately, I've got exception: https://gist.github.com/tmszdmsk/a1b42fdad63ff2fa413f8a31b756a527 I don't have time right now to dig deeper.