Hi there.. I'm just wondering what would be the best way of automating uSync deployments via Octopus Deploy (using uSync version 3.04 for Umbraco 7.3) ?
I'm familiar with Aaron Powell's Chauffeur command line umbraco tool, and I have seen that he's created a uSync addon for it, https://github.com/aaronpowell/Chauffeur.uSync/tree/master/Chauffeur.uSync it sounds good, but I haven't tried it yet, and not sure if it works with this version of uSync. I've spoken with him about how it works though and sounds simple enough. You use the command line to create a snapshot of your uSync configs and then deploy them with a deliverable. He hasn't worked on it in a while though.
You definitely have to use uSync with Octopus for deployment changes in Umbraco database.
It's really good solution, but you need to include all uSync files to your Visual Studio project as I remember.
Also you need to set uSync config to Read from Disc on the start on the dev server for applying changes immediately after deploy.
Hi Alex, I'm already deploying the usync directory to my site using Octopus, but what I would like to do is to run the actual usync import via an Octopus deploy step, by using a command line tool such as Chauffeur or something similar.
I'd prefer to do this as part of the actual deployment process than for these tasks to be performed by the web app on app start.
We're deploying uSync changes successfully via Octopus Deploy, but the same way as Alex, including the uSync files in the deployment and setting the config to Import=true. (We use Octopus Deploy to set Import=true on one server in the web farm but not on the others, so that the import isn't duplicated).
I don't see the need for it to be a separate deployment step. Our first deployment step is a database backup, and we deploy each release of the site to a new folder, so the roll back would simply consist of restoring from the database backup, and re-pointing IIS back to the previous release. Of course this will will re-import the uSync content from the previous release which isn't strictly necessary as it's in the database backup anyway, but no harm done!
Sorry it's not answering your detailed questions, but we find this works well enough without using any other add-ons.
I have one further issue to resolve with Octopus deployments…After deployment, some content is missing and only returns after manually triggering a rebuild of the examine index.
It's odd since the indexes should rebuild on startup since they don't exist and they do appear to since I see the index files on disk. Most site content is present but the most obvious content that is missing is one part of the site that presents content from the ExternalIndex.
Looking at the index it claims to only have a DocumentCount of 6. If I trigger a rebuild it updates to 165.
Nothing much of interest in the logs except for this...
Call was made to RebuildIndexes but the task runner for rebuilding is already running
Automating uSync deployment via Octopus
Hi there.. I'm just wondering what would be the best way of automating uSync deployments via Octopus Deploy (using uSync version 3.04 for Umbraco 7.3) ?
I'm familiar with Aaron Powell's Chauffeur command line umbraco tool, and I have seen that he's created a uSync addon for it, https://github.com/aaronpowell/Chauffeur.uSync/tree/master/Chauffeur.uSync it sounds good, but I haven't tried it yet, and not sure if it works with this version of uSync. I've spoken with him about how it works though and sounds simple enough. You use the command line to create a snapshot of your uSync configs and then deploy them with a deliverable. He hasn't worked on it in a while though.
However, in my searches I've also found https://github.com/thecontrarycat/uSync3.0/tree/master/Jumoo.uSync.Migrations.Chauffeur which seems to be another Chauffeur addon for achieving the same thing.. but some questions about that:
Also, are there any other methods of deploying using Octopus other than these two options I have found?
Thanks..
Hi pantryfight,
You definitely have to use uSync with Octopus for deployment changes in Umbraco database. It's really good solution, but you need to include all uSync files to your Visual Studio project as I remember. Also you need to set uSync config to Read from Disc on the start on the dev server for applying changes immediately after deploy.
Thanks,
Alex
Hi Alex, I'm already deploying the usync directory to my site using Octopus, but what I would like to do is to run the actual usync import via an Octopus deploy step, by using a command line tool such as Chauffeur or something similar.
I'd prefer to do this as part of the actual deployment process than for these tasks to be performed by the web app on app start.
We're deploying uSync changes successfully via Octopus Deploy, but the same way as Alex, including the uSync files in the deployment and setting the config to Import=true. (We use Octopus Deploy to set Import=true on one server in the web farm but not on the others, so that the import isn't duplicated).
I don't see the need for it to be a separate deployment step. Our first deployment step is a database backup, and we deploy each release of the site to a new folder, so the roll back would simply consist of restoring from the database backup, and re-pointing IIS back to the previous release. Of course this will will re-import the uSync content from the previous release which isn't strictly necessary as it's in the database backup anyway, but no harm done!
Sorry it's not answering your detailed questions, but we find this works well enough without using any other add-ons.
We use a transform. To stop content delivery
Export only means you still have uSync files you can grab to get the content back to other envrioments
I'm also doing that at the moment - how do you handle media? Do you have a step to move or copy from the previous release folder?
Virtual directory for media, and App_data. So you dont have to redo all your croppings.
Matt
Thanks @Matt
I have one further issue to resolve with Octopus deployments…After deployment, some content is missing and only returns after manually triggering a rebuild of the examine index.
It's odd since the indexes should rebuild on startup since they don't exist and they do appear to since I see the index files on disk. Most site content is present but the most obvious content that is missing is one part of the site that presents content from the
ExternalIndex
.Looking at the index it claims to only have a
DocumentCount
of 6. If I trigger a rebuild it updates to 165.Nothing much of interest in the logs except for this...
Any ideas?
is working on a reply...