Skip to main content

What is the recommended development and deployment workflow?

How does Front-Commerce Cloud fit in your existing workflow: CI, deployment, tests…

Front-Commerce Cloud is responsible for delivering your code to users.

It follows your Git repository activity and workflow (branching model).

Branches and environments​

There are 3 main deployment environments:

  • production
  • staging
  • preview

Your main branch is for the production environment. It is for the final users.
Your development branch is for the staging environment. It is for your team. If needed, you can also ask Front-Commerce team to create more "development" environments (linked to a specific branch) if required.

Whenever you push code on a branch, it will be deployed on the corresponding environment.

Preview environment​

🚧 Preview environments are currently in beta. They work, but the DX and autonomy is still limited. We're actively looking for feedback from teams using it.

If you have configured the preview deployments using the information provided by the Front-Commerce team (do not hesitate to get in touch with our support to confirm your configuration), then you can initiate a preview deployment by commenting fcc-preview within a Merge/Pull Request.

Preview environments are usually configured to mirror the staging environment, but they can have any configuration. All preview environments share the same configuration.

⚠️ It currently isn't possible to view or update environment variables for Preview environments. Contact us if you need some changes.

Running tests and quality checks​

Front-Commerce Cloud is only responsible for building and deploying your project.

We highly recommend that you also run a Continuous Integration (CI) process using the tools you use on other projects: Gitlab CI, Github Actions, Bamboo, Jenkins.

CI will run your test suite, code linting and other automation ensuring your application is healthy!