Use Mock Pipeline to model value stream maps regardless of your tech stack, cloud provider, or data center. With Mock Pipeline, you can define your value stream map as code in order to visualize all the steps in your commit to production lifecycle. While it uses AWS services/tools such as AWS CloudFormation and AWS CodePipeline, it can model any technology platform.
For a description of the purpose of Mock Pipeline, see Technological Accelerants for Organizational Transformation.
These instructions assume you're using AWS Cloud9. Adapt the instructions if you're using a different IDE.
Fork this repo: https://github.com/stelligent/mock-pipeline
From Cloud 9, clone the newly forked repo (replacing USERNAME in the example).
git clone https://github.com/USERNAME/mock-pipeline.git
cd mock-pipeline
sudo su
sudo curl -s https://getmu.io/install.sh | sh
exit
Make any modificiations to your local mu.yml file (in your Cloud9 IDE in this example) for the stages and actions you want to model. Commit them to your repo.
git commit -am "modify stages and actions" && git push
To create this pipeline in your account, run: mu pipeline up -t GITHUBTOKEN
Your GITHUBTOKEN will look something like this: 2bdg4jdreaacc7gh7809543d4hg90EXAMPLE. To get or generate a token, go to GitHub's Token Settings.
After a few of the CloudFormation stacks have launched, go to the CodePipeline console and look for a pipeline with something like mock-pipeline in its name. Select this pipeline and ensure you are properly connected to the GitHub repository you'd previously forked.
See Metric Details for more information on release metrics such as Cycle Time, Lead Time, and MTTR.