March 2019
Intermediate to advanced
636 pages
27h 50m
English
You may recall that in our promotion process, we identified two events within the life cycle that were meant to trigger the pipeline:
Some may wonder why only these events were specifically chosen. If you recall the process, the developers are expected to manually run tests on their local environment, so there is not an absolute need to trigger the pipeline every time someone delivers code to their own branch. However, when initiating the process of delivering the code to the master branch, it is important to validate that the code can be built, deployed, and tested before accepting changes to the master branch. The same goes with tagging a release—this is an indication that a new ...
Read now
Unlock full access