3 ms·
It probably depends on exactly what and how complex your “transformation” is. You definitely can do lots of automation with $ git itself in terms of committing
by tedmiston 9y ago
It probably depends on exactly what and how complex your “transformation” is. You definitely can do lots of automation with $ git itself in terms of committing, merging, opening PRs on GitHub via $ hub, etc.
Another idea is if you can refactor the common bits into a shared standard library, for instance the design pattern is something like a system with a bunch of plugins, then most of the plugin repos become very tiny. Ideally you’d also have some sort of infrastructure automation around deployment.
- Sevii 9y agoWe have shared libraries and maven plugins setup. This is a situation where I really wish we used a monorepo and I could just do one commit across 100 microservices using grep and other tools to update pom.xml files. I have read whitepapers from google on how they support this kind of operation, but I need it for many git repos.
- ynezz 9y agoThis sounds like StackOverflow question. Anyway, if you're proficient in Java, why don't you write small app which will iterate over all Git repo dirs, modifies the files, makes commit, push and creates PRs? Not a big deal, right?
- Sevii 9y agoThat is the current plan, combined with plenty of manual work verifying jenkins jobs and deployments.
- assafmo 9y agoIf you can do it if there was just one repo, then juat clone those 100 repos under the same parent directory and execute the script in the parent directory
- assafmo 9y agoand then in a loop commit the changes