Hi there,
Thanks for adding this!
“- The Deadline Client can now override the Repository’s auto-update setting in its deadline.ini file.”
What ini entry do we need to use for this?
Also, is it possible to add an alternate path for the binaries to update from? (remote locations could have their own local servers for the binaries)
cheers,
laszlo
The .ini setting is AutoUpdateOverride. ‘AutoUpdateOverride=True’ will force auto-updates to on for that machine, where ‘AutoUpdateOverride=False’ will prevent them on that machine. A blank (‘AutoUpdateOverride=’) or missing value will just defer to Repo options, the way it does normally.
In terms of separate locations for binaries, we do not have any direct support for this. You could create a separate (remote) repository, and point remote machines to that one, while still using the same Database. The problem with this setup comes in with different locations accessing the same logs/plugins/job aux files, but you could probably set up some clever mount points inside your new repo to keep that the same. Obviously a bit of a complex set up just to synch binaries from a local server, but it could theoretically be done…
Cheers,
Hmm, thats a good idea, we could basically mount all the folders off the ‘main’ repo, except the binary / scripts folders, and update those manually when needed.
Could the ‘alternative central binary location’ as an auto-configuration option be added to the wishlist?
I suspect this will be a bit of a pita for us to manage with multiple locations (but a single remote repository).
Basically the whole repo would be treated as remote, but for the main binaries (the bin folder in the repo), we could define an alternative location. The auto configuration would then let us set up a rule based on the IP ranges as to what server to use to pull the binaries.
We might actually manage that via svn/git etc.
Yeah, we can totally add that to the wishlist.
Cheers,