I have Studio 21.4.4 and Orchestrator 21.4.2. How is it possible that an empty project from a standard Studio template is including packages (such as Google ones) that Orchestrator doesn’t have? This is infuriating, especially so as Orchestrator actually has newer versions of the ones that are ‘missing’ in a lot of cases. Is there a way to include the actual dependencies with the project when it’s published? Why are there so many version mismatches between what’s in Orchestrator and what’s in Studio when the versions are nearly identical?
It doesn’t work that way, Studio doesn’t get them from Orchestrator. In fact, there’s no reason to have any packages in Orchestrator except custom libraries.
When building a project in Studio you decide which packages (dependencies) and which versions are used in the project. This is all stored in the project.json file. When you publish to Orchestrator the dependencies don’t go with the project, just the info in project.json. When the Job is run on a particular machine (either attended via Assistant, or unattended via Orchestrator) the Robot.exe process reads project.json and downloads the packages directly from the online repositories.
Hey @Craig1
Did you enforce or enable some studio settings to include those packages when a project is created ?
Thanks
#nK
The robots are also able to get them from Orchestrator. If you add a missing package to the Orchestrator library the dependency will be satisfied. If that wasn’t the case why would Orchestrator be supplied with a load of packages under libraries?
Is there a way to do that? It would be useful to include the dependencies for robots that do not have internet access.
Yep @Craig1
You wanna disable outside packages right ?
I would like there to be an option for that, yes.
Hello @Craig1
You can try disabling the Market place from the feed.
How do I then bundle the dependencies with the package?
Sorry @Craig1 Unable to get you ?
It doesn’t matter, but granting access to myget.org for the robot servers didn’t help.