3

The new PaaS solution of Magento Enterprise 2 has just been released, "Magento Enterprise Cloud Edition". Other than with Magento Go, you have full access to the source code and you can do whatever is possible with Magento EE. As I understand it, the cloud edition is a set of pre-built tools and configurations on top of AWS:

enter image description here

(Image: https://magento.com/products/enterprise-cloud-edition)

Now my question is, which third-party tools, if any, are used for:

  • Continuous Integration
  • Rapid Deployment
  • Dev Life Cycle Management
  • Environment Management

And if it's all proprietary, will it be possible to integrate other systems as replacement, for example, if we have an existing Jenkins or Bamboo setup for CI?

  • 1
    there is nothing just a blind marketing, Magento again going the way they should not GO. i wonder how it affects their hosting and integration partners?? what for exactly they paid their partner fees, so magento just sold its cloud edition solely to platform.sh and AWS. – MagenX Apr 13 '16 at 7:37
  • Ah, I didn't know platform.sh - judging by first look on their site, all the marketed features are actually platform.sh features and "Magento Enterprise Cloud Edition" is merely a giant mashup. – Fabian Schmengler Apr 13 '16 at 7:41
5

From what I've gathered at the sessions and demos with the Cloud booth at Imagine 2016, you can use any tools and processes you want to use. If you already have processes implemented, they should not need to change (much).

The way the solution was presented was that you have a master git repo and within the web UI supplied by Platform.sh you create as many branches as you need. So you can have a branch for staging, and a branch for development. Then under those branches, you can have as many branches as you have features. It's a one-click deployment of a replica of the production system for your one feature. Each branch generates, at that time, a new environment which replicates the production environment.

So you do your code development after creating a branch within the new Platform.sh web UI and commit your code to that branch. Once it's passed your tests, you push up to the remote and your branch environment has the new code deployed to it (possibly through the web UI or done through git hooks). Each environment has a unique URL which you can then use to review that specific feature's changes.

The platform is proprietary; however, they have done as much as possible to make it as flexible as can be. The recipes used for creating deployments can be edited by you. There is also an easy way to add/remove environment variables for scripts so you can change the database credentials or sanitize all the data in the database if need be on each deployment.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.