Page History

If you have opted for a custom cloud bundle variant, your site is hosted in Magnolia Cloud and you or your partner manages the creation of custom Java modules and the creation and deployment of the custom bundle.  ++++light dev can be done in parallel with java/light dev in custom bundles since the light dev is stored in git and can easily be reinstalled.

Continuous delivery is a way to ensure that new configuration, templates and code can be rapidly and safely deployed to production. You deliver every change first to a UAT environment and verify that business applications and services function as expected through testing. Since every change is delivered to the UAT environment using automation in the Magnolia Cloud Cockpit, you have confidence that the application can be deployed to the Live environment exactly the same way, with a push of a button when the business is ready. In the UAT environment, business users can validate your changes with real content cloned from the Live environment. – Adapted from Caum, Carl: Continuous Delivery Vs. Continuous Deployment: What's the Diff?

• You or your cloud partner set up the maven project reactor following the readme instructions
• You deploy the custom bundle to Magnolia CLoud. 

...

• First upgrade from standard bundle to a custom bundle is effort intensive on mgnl side due to dependency/compatibility issues. Only if data must be kept. Simpler alternative is to remove and replce when data doesn't need to be kept.
• Change in bundle name triggers same effort. +++Warning to not change name unless absolutely necessary.
• Partner bundle upgrade to newer partner bundle is fine.
• Mention: light dev can be done in parallel with java/light dev in custom bundles since the light dev is stored in git and can easily be reinstalled

...

To successfully deploy For customers deploying custom bundles to Magnolia Cloud certain criteria and best practices have to must be adopted.

Project setup and best practices

...