LogoLogo
  • Planet 4
  • Development
    • Contribute
    • Installation
    • Git Guidelines
    • Coding Standards
    • Continuous Delivery
  • CI/CD
    • Test Instances
    • Deployment
    • Testing
      • End-to-end Tests
      • Visual Regression Tests
  • NRO Customization
    • Development
      • Using Child Themes
      • Package Registry
      • Plugins
    • Testing
      • Visual Regression Tests
    • Deployment
      • Production
      • DB/Media Sync
  • Infrastructure
    • NRO Generation
    • ElasticSearch
    • Cloudflare
  • Recipes
    • Maintenance page
    • Production sync
    • Running commands
  • Platform
    • Practices
    • ADRs
      • [ADR-0001] Use Gitbook for Technical Documentation
      • [ADR-0002] P3 Archive elastic search integration
      • [ADR-0003] WYSIWYG Blocks Architecture
      • [ADR-0004] Switch to Monorepo
      • [ADR-0006] Define scope for deployment environments
      • [ADR-0008] PSR-4 Autoloading Standard
      • [ADR-0009] Include Media Library in master theme
      • [ADR-0011] PHP Coding Standards
      • [ADR-0012] Use custom SCSS syntax for variables
      • [ADR-0013] Choose a ticketing system
      • [ADR-0014] Choose a testing framework
      • [ADR-0015] Use block templates to build block patterns
      • [ADR-0016] Form Builder data retention policy
      • [ADR-0017] Move blocks into the theme
    • Changelog
      • 2024
      • 2023
      • 2022
      • 2021
      • 2020
      • 2019
      • 2018
  • Tech
    • Wordpress
    • Blocks
    • Plugins
    • Hooks
    • Data migrations
    • CSS variables
Powered by GitBook
On this page
  • Development Cycle
  • Git branching model
Edit on GitHub
  1. Development

Continuous Delivery

A quick overview of the development cycle

PreviousCoding StandardsNextTest Instances

Last updated 2 years ago

Definition: Continuous Delivery (CD) is a software development methodology in which software iterations are delivered frequently through unscheduled deployments. The final production deployment step is done manually, but the main idea is that the code merged is potentially production-ready, and a new release can be deployed at any time.

At Planet 4 we adopted CD in order to be able to deliver quick iterations and move faster. We try to follow the well-known Open Source principle: "Release early, release often".

Development Cycle

From the moment some new Code is pushed to one of our repositories till that being deployed to production. Once a new Pull Request is created, automated tests and peer code review is taking place. The engineer assigned to work on this uses a test instance to deploy the change, so other people from the team can verify it during User Acceptance Testing (UAT).

Git branching model

Our Git branching strategy is following Github-flow, where there is only one main branch (main). That branch always has code ready to be deployed in production.

Development Cycle
Github Flow