Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Here is the example pipeline we will talk at high level. It is entirely up to process that you want to implement in your organization, this is just one example.

In this pipeline, we will have 4 roles which makes up our Team.

High Level Approach

Here is high level approach, in next section we will show screen shot for each Gate and Step.

  • There are 4 stages - Development, Test, QA and Production.
  • Development stage does not have any Gates, so all projects will deploy right away when new Release Snapshot is created.
  • Run various types of tests in each Stage and check for results on next stage.
  • Test environment is based on Schedule, but QA is based on approval by QA team to make sure they are ready to accept new code.
  • All steps in pipeline are automated except there is a step in QA to perform some Manual tests.
  • Production environment has Approval as well as Schedule. Weekend schedule allows for automated deployments at appropriate time.
  • Deploy All step will notify appropriate team on Failure in each Stage.

Stages

Development

Test

QA

Production


  • No labels