updateing deadline workflow

[anon7385795]

sorry if the answer to this is already documented,

We are currently running an older beta version of deadline7.
It has a few bugs (which I understand have been solved) and its about time we changed to a proper production release.

This is what it says in the help tab:

Deadline Version: 7.0.0.33 R (d065b23bf)
FranticX Version: 2.1.0.0 R (7bee7b4e3)

What is the process off updating to the latest stable release?

[LaszloSebo]

My usual workflow is to update the central repository, then let auto-updating take care of the slaves themselves.

The method i most commonly use is:

• Install the repository on my local machine somewhere, pointing it to the same database as the live repository has
• Delete the settings/dbConnect.xml file from my local machine repository installation
• Delete the reports / jobs / jobsArchived folders from my local machine repository installation (they are empty folders but take some time to copy due to all the subfolders)
• Merge any code changes i might have made
• Copy the folders from my local repository installation to the live repository, overwriting the files there

As long as you have the slave auto updating turned on, they will update to the latest version on their next restart. You can issue the remote restart commands through the monitor.

[MikeOwen]

Yep, Laszlo’s workflow is fine, especially if you have lots of custom stuff you need to manually merge/diff-compare on.
Here’s our official docs page:
docs.thinkboxsoftware.com/produc … downgrades