I don't think this has much to do with Magnolia itself, but rather how 
you want to setup your continuous integration environment. I would 
recommend something like the following:

- Use git as a shared code repository

- Make sure that developers create for every little feature or bug a branch

- Make sure that developers break down development into small enough 
junks that they can merge their "feature/bug" branches into the master 
branch at least once day

- Connect your master branch with Jenkins which is executing all the 
automatic tests for all changes made on the master branch

- If you have more than five developers, then find a dedicated person 
which does nothing than making sure that automatic tests are being 
written and updated continuously (including performance/scalability tests)

- Release the master branch on the testing environment when all 
automatic tests are successfull, which actually *always* should be true, 
assuming the developers are running tests before merging into the master 
branch

- Release early and often on the productive environment (if possible 
every 1-3 days), because the real thing will always
show things which neither automatic nor user acceptance tests will show.

The trick is simple, the shorter the interval, the smaller the changes, 
the smaller the risk that something will break which will be hard to fix 
or not reversable.

Of course there are more details to it, but these are the main building 
blocks I would recommend.

HTH

Michael

Am 11.06.13 19:40, schrieb Magnolia Developer (via Magnolia Forums):
> Hello ! I want to know if there is a way to create a perfect structure to 
> create a Magnolia Project using Continuous Integration. The project is very 
> big and there are more than five developers.
>



----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to