Action Point Dashboard
  • Action Point Dashboard Documentation
  • INTRODUCTION
    • Glossary / Terminology
    • FAQ
    • Releases / Changelog*
    • Report an Issue / Contact us
  • PRODUCT / END-USER DOCUMENTATION
    • Overview
      • Objectives
      • User roles and permissions
    • Action Points Dashboard Navigation
    • Overall User Interface
    • List of Action Points
    • Action Points Workflow
    • Action Points
      • Creation of Action Point
      • Modification of Action Point
      • Completion of Action Point
      • Additional options for Action Point
    • Connections to other modules
      • Overview
      • Action Points in FAM
      • Action Points in Field Monitoring
      • Action Points in TPM
      • Action Points in Trip Management (T2F)
  • TECHNICAL DOCUMENTATION
    • Architecture
    • Development Setup
    • Deployment / DevOps
    • Data Model
    • Fixtures & management commands
    • API Documentation
      • Error Handling
    • Backend module structure
    • Integration with permissions framework
    • Frontend
      • Module structure
      • Build process
      • Tests
Powered by GitBook
On this page
  1. TECHNICAL DOCUMENTATION

Deployment / DevOps

PreviousDevelopment SetupNextData Model

Last updated 6 years ago

From a development standpoint we follow the standard git flow doing Pull Requests (PR's) for changes, code review and then merging to develop (the integration branch for testing / staging environments) and master (stable) branches.

Once the code has been merged to develop/master, it is automatically deployed to the staging/production using the following tooling/flow:

CI is done in CircleCI where images are built and tests are run. CircleCI then pushes the various images to Docker Hub, which is then automatically picked up by the appropriate "stack" in Docker Cloud.