GIT with Dependency Mass Update Tool

Help Studio
, ,
1

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
2

Hey @Bill_Richardson

Did you tried using this please ?

Thanks
#nK

3

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
4

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
5

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

6

I think this is how it behaves for now.

7

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

2 Likes
Mass update doesn't see robot information from Group in GitLab
8

Okay will check check the possibilities for it

9

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.

10

Any News ? I Need this Option too.

11

Please explain ? @power

13

The way we handle updating multiple repository dependencies is by using batch files (BitClone, BitCommit and Repo_List) along with the Dependency Mass Update Tool.

  1. We first run BitClone, which will clone our repositories to a newly created UiPath_Cloned_Repositories folder.
  2. We then use the Dependency Mass Update Tool to update all of the cloned repository dependencies in the UiPath_Cloned_Repositories folder.
  3. Lastly, we run the BitCommit batch file to commit the changes to BitBucket.

The Repo_List batch file contains our list of repositories.

Arguments for the batch files are: user directory name, bitbucket un, bitbucket pw, Demo_or_OTS_or_Custom (self-defined type of repository)

**BitClone.bat:**
@echo off

setlocal
CALL Y:\UiPath_Final\Batch_Files\Repo_List.bat %4
set destination=C:\Users%1\Documents\UiPath_Cloned_Repositories

powershell -Command “Remove-Item -Path '”%destination%“’ -Recurse -Force”
mkdir “%destination%”

for %%r in (%repos%) do (
echo Cloning %%r…
git clone https://%2:%3@bitbucket.org/mtdevs/%%r.git “%destination%%%r”
if errorlevel 1 (
echo Failed to clone %%r
) else (
echo Successfully cloned %%r
)
)

echo Git clones executed.
endlocal

**BitCommit.bat:**
@echo off

setlocal
CALL Y:\UiPath_Final\Batch_Files\Repo_List.bat %4
set destination=C:\Users%1\Documents\UiPath_Cloned_Repositories

for %%r in (%repos%) do (
echo Commiting %%r…
cd C:\Users%1\Documents\UiPath_Cloned_Repositories%%r
git add .
git commit -m “Changes to library version in .json file”
git push
if errorlevel 1 (
echo Failed to commit %%r
) else (
echo Successfully committed %%r
)
)

echo Git commits executed.
endlocal

**Repo_List.bat (partial):**
::
:: Demo Storylines
:: ---------------
::
if %1==Demo (

set repos=^
acute_heart_failure_demo ^
acute_hip_replacement_demo ^
ankle_fracture_patient_demo ^
bh_bipolar_demo ^
bh_restraint_demo ^
bh_schizophrenia_demo ^
case_management_demo ^
critical_care_demo ^
ed_abdominal_pain_demo ^
ed_chest_pain_demo ^
ed_heart_failure_demo ^
ed_pediatric_patient_demo ^
.
.
webamb-rx-refill-demo)