GIT with Dependency Mass Update Tool

Is there a way to have the Dependency Mass Update Tool look at multiple repositories on one run? It’s nice that there’s now an option to look at a GIT repository, but since it seems like the only way to use repositories with GIT is to have one per automation source, I would end up running the update tool once for each of my sources, which would defeat the purpose of the mass update tool.

3 Likes

Hey @Bill_Richardson

Did you tried using this please ?

Thanks
#nK

Yes–I’ve read that documentation. It does work, but at least with GIT, you can only select one repository. I have one set of source code per automation per repository. There doesn’t seem to be a way to select multiple repositories.

1 Like

Bumping this because I’m in the same boat. Each project in my org has its own repo so the mass update tool only works if I provide the path the a specific project repo. This would require that I run the “mass” update tool for for every project, defeating the purpose.

Any ideas would be great :slight_smile:

1 Like

So @everydayRPA

You have an organization setup in git with n number of repos available.

You wanna do bulk update packages for those.

Is that correct !

Thanks
#nK

I think this is how it behaves for now.

Yes–It would be nice if the mass update tool could work over multiple repositories.

2 Likes

Okay will check check the possibilities for it

Any new on the subject? We have multiple projects grouped together within a group in git. Unfortunatelly the mass update tool is not able to find any projects within a group.