Fileset Revisions Overview
What
Fileset (payload) revisions allowlet you maintainkeep two (or more) differentmore versions of the same fileset withinor onepayload inside a single FileWave fileset object.
When/Why
The above description might not knock your socks off, but weRevisions are prettyuseful excitedwhen abouta this,payload andchanges thinkover time, especially for application upgrades.
For example, assume you will be too! Consider this scenario:
We are currently deploying Firefox (v79)v79 and need to all of the devices in the environment. But v80 oftest Firefox isv80. nowWithout out,revisions, andyou we want to upgrade. Previously we had to eithermight duplicate the FileWave fileset and change the content of it, or create a brandnew one, move test devices to a new filesetassociation, fromand scratch.then replace Then,the whenproduction weassociation hadafter testing. If timing matters, that can turn into a careful shuffle to removeavoid interrupting users.
With fileset revisions, v80 can live in the same fileset that already contains v79. You can then choose which revision an association uses, instead of replacing the whole fileset or rebuilding the association for v79 from our test devices and add a new association for v80. And, assuming all was good, we then had to remove the old association for all devices, and replace it with the new one. Finally, if we were worried about the possible interruption of service by removal of the old app, we might have had to play a bit of a shell game with the timing to make sure customers weren't impacted by the upgrade.
Not anymore!scratch.
How
FilesetWhen revisions allow you put version 80 of Firefox in the very samea fileset inhas whichmultiple you had v79. Then, rather than removing associations, you would just change the revisionrevisions, the association uses.workflow And, we take care all of that complicated fileset timing stuff for you. In subsequent articles (linked below), we'll go into all of the specifics, but here is a sneak preview of settingincludes a revision inchoice. anIn association:the example below, the association can use the default revision, the initial revision, or the newer v80 revision:
You maydo be thinking to yourself: "This sounds complicated, and I don't want to use revisions." There are two responses: First, you absolutely don'tnot have to use themfileset if you don't want to. revisions. If you choose to ignore revisions, then everything willfilesets continue to work exactly the way itthey hasalways forhave. When you indo theneed past.staged application Restupdates assuredor though,controlled Filesettesting, revisions aren't actually complicated, and you may find they reallycan make thingsthat easierworkflow for you.cleaner.