Skip to content

Pipelines

Environments

Depending upon the project there will be one or more shared enviroments set up.

  • Development(DEV)
  • QA(QA)
  • Staging(STAGE)
  • Production(PROD)

Branches

There will be one or more branches set up for each code repository.

  • Development(develop)
  • Main(main)
  • Features(features)

Pipeline Deployments

Code branches will typically be configured to deploy to the environments via CI as follows:

diagram

Notes:

  • The development branch is typically the default branch for the repository.
  • To add new code, a new feature branch should be created from the development branch.

    Example: /features/feature-XXXXX-Brief Description
    - XXXXX is the Ticket/Task Number

  • Updated code should be committed regularly/daily to the newly created feature branch.
  • Upon completion of the feature, a Pull Request should be created.
  • A Code review will be performed on the Pull Request.
  • Upon approval the code will be merged into the development branch.
  • The code will then be deployed to the development environment for review and testing.
  • After review and successful testing, the updated code will be deployed to the QA environment.
  • QA will be performed.
  • Any defects will be sent back to development for resolution.
  • After successful QA testing, the updated code will be deployed to the Staging environment in coordination with the customer and any trading partners or other parties that may be affected.
  • Customer will review and provide any User Acceptance Testing(UAT).
  • After any User Acceptance Testing has been completed successfully, the updated code will be deployed to the Production environment in coordination with the customer and any trading partners or other parties that may be affected.
Back to top