Summary

Hopefully, this chapter has given you a good overview of the challenges and considerations required to align a consortium around the promotion process. CI and CD pipelines are an essential part of providing velocity to a consortium, removing manual processes, and ensuring that every organization can review and approve code changes before they go live. We've looked at some of the key events, such as pull requests and tag releases.

Over the course of this chapter, you have configured a complete CI pipeline, including testing and publishing the chaincode archive. Furthermore, you have seen how we can secure the production-ready code by protecting the master branch, as well as ensuring that every change is subject to a code review by key participants from organizations. We have also looked at how we can ensure we maintain the provenance of each Git commit using a GPG signature. Finally, we have reviewed a process used to deploy updates in a trusted manner.

One thing...