Book Image

Blockchain Development with Hyperledger

By : Salman A. Baset, Luc Desrosiers, Nitin Gaur, Petr Novotny, Anthony O'Dowd, Venkatraman Ramakrishna, Weimin Sun, Xun (Brian) Wu
Book Image

Blockchain Development with Hyperledger

By: Salman A. Baset, Luc Desrosiers, Nitin Gaur, Petr Novotny, Anthony O'Dowd, Venkatraman Ramakrishna, Weimin Sun, Xun (Brian) Wu

Overview of this book

Blockchain and Hyperledger are open source technologies that power the development of decentralized applications. This Learning Path is your helpful reference for exploring and building blockchain networks using Ethereum, Hyperledger Fabric, and Hyperledger Composer. Blockchain Development with Hyperledger will start off by giving you an overview of blockchain and demonstrating how you can set up an Ethereum development environment for developing, packaging, building, and testing campaign-decentralized applications. You'll then explore the de facto language Solidity, which you can use to develop decentralized applications in Ethereum. Following this, you'll be able to configure Hyperledger Fabric and use it to build private blockchain networks and applications that connect to them. Toward the later chapters, you'll learn how to design and launch a network, and even implement smart contracts in chain code. By the end of this Learning Path, you'll be able to build and deploy your own decentralized applications by addressing the key pain points encountered in the blockchain life cycle. This Learning Path includes content from the following Packt products: • Blockchain Quick Start Guide by Xun (Brian) Wu and Weimin Sun • Hands-On Blockchain with Hyperledger by Nitin Gaur et al.
Table of Contents (25 chapters)
Title Page
Copyright
About Packt
Contributors
Preface
Index

Configuring a continuous integration pipeline


Not all languages are created equal, and while we could debate the benefits of strongly typed languages such as Java and Go versus untyped ones such as JavaScript, the fact is that we need to rely on unit tests to ensure that the code is working as intended. This is not a bad thing in itself—every code artifact should be supported by a set of tests with adequate coverage.

What does that have to do with a continuous delivery pipeline, you may be wondering? Well, it's all about the tests and, in the case of JavaScript code, this is very important. While pipeline will need to ensure the following:

  • The code is meeting all quality rules
  • All unit tests are successful
  • All integration tests are successful

Once these steps are successful, then the process will be able to package and publish the result.

So, in the next sections, we will experiment with the deployment and configuration of our pipeline using one of the popular cloud-based continuous integration...