Multi-Team Development with EPiServer



How do you manage developement process if you have several teams with lots of developers on the same EPiServer-based projects. What are the best practices in this case? I am talking from the EPiServer DataBase point of view.

Thanks in advance.

Oct 08, 2014 23:07

Hi this is a late reply but I thought I give you my opinion.

Regarding database I tend to recommend developers to keep their own db at the beginning of the projects for a couple of weeks. I do that because the fact that we usually change the definitions of pages and blocks a lot in the beginning of a project. If a developer starts to work with "my" things we might end up the need of manual work to either install a new db or rollback properties on contenttypes. The reason for this is that once an object has been used by an editor we might not be able to change things in code anymore.

After a couple of weeks when things are more up to speed I sugest working togheter on the same database. But still I prefer having a local db :)

Feb 04, 2015 20:17

We use the shared database and assets folder from day one :)

Usually two developers don't work on the same page type / block / view at the same time.
When they do, then every developer creates a new page in edit mode for testing -> JohnTest, MikeTest, etc.

We also have a definition of done by which we have to test everything locally and on the test server before we resolve an issue in Jira.
Having a shared database saves us a lot of time.

Edited, Feb 04, 2015 20:36
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.