Skip to main content

Documentation Index

Fetch the complete documentation index at: https://platform.docs.zenoo.com/llms.txt

Use this file to discover all available pages before exploring further.

Zenoo’s software development lifecycle (SDLC) emphasizes automation, testing rigor, and compliance with best practices to ensure high-quality, secure, and reliable software delivery. This process is seamlessly integrated with our build and deployment pipeline.

​
Development Workflow

  1. Version Control: Development is managed via GitHub repositories.
  2. Pull Requests (PR): All code changes are submitted through PRs, ensuring:
    • Peer reviews for quality and correctness.
    • Documentation updates are included.
  3. Approval and Testing:
    • PRs are reviewed and approved.
    • A build is triggered, executing unit and integration tests.
  4. Deployment Process:
    • Once tests pass, the latest version is released.
    • A Docker image is built, and frontend assets are compiled.
Environments

​
Deployment Pipeline

Zenoo uses a robust, automated CI/CD pipeline via GitHub Actions, enabling consistent and efficient deployment to the following environments:
  • Development (DEV):
    • Applications undergo end-to-end Cypress testing.
  • Testing (TEST):
    • Further end-to-end tests are executed to ensure stability.
  • Staging (STAGE):
    • QA and UAT testing is performed using provider sandbox accounts for validation.
  • Production (PROD):
    • Deployments proceed after all necessary approvals.
Each deployment phase ensures that the application meets quality and security standards before advancing to the next stage.

​
Container Management and Security

  1. Containerization:
    • Docker containers encapsulate applications, enabling portability and consistency.
  2. Registry and Scanning:
    • Built containers are pushed to a shared container registry.
    • Security scans are conducted on every push to identify vulnerabilities.

​
Key Highlights of Zenoo’s Build and Deployment Process:

  • Testing Automation:
    • Unit, integration, and end-to-end testing are embedded in the CI/CD pipeline.
  • Security:
    • Containers are scanned for vulnerabilities.
    • Secure configurations ensure safe deployments.
  • Environment Segregation:
    • Development, testing (QA), staging (UAT) and production environments are isolated to mitigate risks and ensure compliance.
  • Monitoring and Alerts:
    • Automated monitoring provides feedback on deployments and application health.
  • Rollback Procedures:
    • Robust rollback plans are in place to ensure minimal disruption in case of failure.
By integrating these practices into our SDLC, Zenoo maintains agility and quality while adhering to security and compliance standards.