CI/CD Pipeline

Fransys includes a complete CI/CD pipeline. The initial configuration (Git connection, pipeline generation) is handled automatically during the setup of your application blocks.

→ For the initial setup, see Application Blocks

This page details the deployment process once CI/CD is in place.

How a deployment works

When you trigger a deployment (push to the configured branch or manual deployment), Fransys executes the following steps:

1. Build — The Docker image of your application is built from your source code
2. Push — The image is pushed to the internal Fransys registry
3. Deploy — The Kubernetes cluster updates the pods with the new image
4. Health check — Fransys verifies that the new version responds correctly
5. Automatic rollback — If the health check fails, the previous version is restored immediately

You don't have to configure any of these steps — everything is managed by the automatically generated pipeline.

Deployment queue

Deployments are queued. If you push several commits quickly or if multiple blocks are updated simultaneously, deployments are stacked and executed in order.

This mechanism ensures that a deployment is always completed before the next one begins — no conflicts, no unstable intermediate states.

Automatic rollback

If a deployment fails (the application doesn't start, the health check doesn't pass), Fransys automatically rolls back to the last stable version. Your application remains accessible — no service interruption.

Deployment commands

Application blocks have a Deployment commands tab that lets you define commands executed automatically with each deployment. For example:

• Database migrations (php artisan migrate)
• Asset builds (npm run build)
• Cache clearing (php artisan cache:clear)
• Seeds or initialization scripts

These commands are executed after the new image is deployed and before traffic is switched to the new version.