To get scripts use
PM> Export-EPiUpdates 
Run those manualy or add into some installer

Read the last few comments http://world.episerver.com/Articles/Items/EPiServer-Continuous-Release-Process/

/K

Hi.

unfortunalety I get the same error, when I try to run it:

"Found no files to process"

In the exported folders is only one file: 7.6.0.0.config



Thorsten

Hi. 

Got the same problem but found the cause.

EPis update command scans all packages in the nuget packages folder and searches for tools/epiupdates folders and runs all sql scripts in the tools/epiupdates/sql folder.

In my case we had all packages commited to git but the .gitignore file template that we used had excluded the sql/ folder.

(In my case the EPiServer.CMS.Core.7.13.3\tools\epiupdates\sql was not present)

Removing the restricition in gitignore and restoring the package to get back the sql updates, did the trick...

Running Export-EPiUpdates in nuget console creates a folder called EPiUpdatePackage which contains the SQL scripts to be run. But you don't need to run them manually (and probably shouldn't). You simply run update.bat and it will patch both CMS and Commerce database. To upgrade other environments, simply copy this folder and run update.bat.

See http://world.episerver.com/Documentation/Items/Developers-Guide/EPiServer-CMS/75/Deployment/Updating-EPiServer-via-NuGet/

I'm experiencing the same "Found no files to process" error message on a server.

Scenario:

Web server with an upgraded project deployed. Database is at version 7006, needs to be at 7007.

Ran Export-EPiUpdates locally and copied the files/folder to the server. 

The exported folder contains a single file: \EPiServer.CMS.Core.7.8.2\epiupdates\config\7.6.0.0.config

Executed update on the server with the path set to the website root.

This results in the "Found to files to process" error.

Appreciate any input! :)

Check the  packages\EPiServer.CMS.Core.7.13.3\tools\epiupdates\sql folder (or what version you have).

There should be a 7.8.0.sql script there.

If not, your nuget package is not complete.

Had the same issue where we commited our packages to git and where the .gitignore ignored the sql/ folder.

I had this error aswell, likely caused by git, like Dan experienced.

The error occured when using a package through git and depoyment.

When I created a new update package and copied it instead, it worked.