We recently started working with Umbraco on a small site and I was wondering if anyone has a clean build and release workflow or some insights that can help us integrate Umbraco in our CI process.
We use TFS to build the code and package it but are not completely sure how to migrate DocumentTypes of if we even should.
Is it possible to automate the creation of packages at all (The ones generated by Umbraco)? We currently do this manually from a running instance but find it tedious and error prone.
This package serializes data that is stored in the database to xml files. You can deploy these files to different environments and on startup all your config will be imported
We're using uSync and it works like a charm! When we create new templates or dictionary items in our dev evnironment uSync creates xml-files in its designated folder and when we deploy to production, those xml files follows along and gets imported. uSync allowes you to configure how it should work, so you can configure it to only sync on demand and not automagically.
Build and release workflow
Hi all,
We recently started working with Umbraco on a small site and I was wondering if anyone has a clean build and release workflow or some insights that can help us integrate Umbraco in our CI process.
We use TFS to build the code and package it but are not completely sure how to migrate DocumentTypes of if we even should.
Is it possible to automate the creation of packages at all (The ones generated by Umbraco)? We currently do this manually from a running instance but find it tedious and error prone.
Thank you! Matei
Hi Matei,
For deploying doctypes, datatypes, dictionary, ... between our environments we use https://our.umbraco.org/projects/developer-tools/usync/
This package serializes data that is stored in the database to xml files. You can deploy these files to different environments and on startup all your config will be imported
Dave
Hi Dave,
That looks promising, thank you! Will give it a try shortly.
Matei
We're using uSync and it works like a charm! When we create new templates or dictionary items in our dev evnironment uSync creates xml-files in its designated folder and when we deploy to production, those xml files follows along and gets imported. uSync allowes you to configure how it should work, so you can configure it to only sync on demand and not automagically.
Thanks guys! I forgot to follow up on this but uSync has indeed been working for us very well! Thanks again!
is working on a reply...