Hopefully, this chapter will have given you a good overview of the challenges and considerations required to align a consortium around the promotion process.

Continuous delivery pipelines are an essential part of providing the 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 the pull request and the tag release.

Over the course of this chapter, you have completed the configuration of a complete continuous integration pipeline, including testing and publication of the business network archive. Furthermore, we have seen how we can protect the production-ready code by protecting the master branch and 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 gpg signature. Finally we have reviewed a process to deploy updates in a trusted manner.

One thing is sure: automation is the key to agility—by eliminating repetitive manual tasks and providing a structure to how we modify the code, we enable organizations to be more agile and respond quickly, whether to defects or new requirements. This chapter was, of course, only a small introduction to this approach and its associated concepts; some of these topics could warrant their own books.