concept infrastructure in category gradle

This is an excerpt from Manning's book Gradle in Action - corrected 9052019.
Gradle provides an infrastructure to manage the complexity of resolving, retrieving, and storing dependencies. Once they’re downloaded and put in your local cache, they’re made available to your project. A key requirement of enterprise builds is reproducibility. Recall the story of Tom and Joe from chapter 1. Do you remember the last time your coworker said, “But it works on my box”? Builds have to produce the same result on different machines, independent of the contents of your local cache. Dependency managers like Ivy and Maven in their current implementation cannot fully guarantee reproducibility. Why is that? Whenever a dependency is downloaded and stored in the local cache, it doesn’t take into account the artifact’s origin. In situations where the repository is changed for a project, the cached dependency is considered resolved, even though the artifact’s content may be slightly different. At worst, this will cause a failing build that’s extremely hard to debug. Another common complaint specific to Ivy is the fact that dependency snapshot versions, artifacts currently under development with the naming convention –SNAPSHOT, aren’t updated correctly in the local cache, even though it changed on the repository and is marked as changing. There are many more scenarios where current solutions fall short. Gradle provides its own configurable, reliable, and efficient dependency management solution. We’ll have a closer look at its features in chapter 5.
All of these processes—deployment to different environments and the verification of a successful deployment—need to be part of your build pipeline. After setting up the supporting tasks in Gradle, you can invoke them from corresponding jobs in Jenkins. Deploying software for authorized stakeholders within an organization should be as easy as pushing a button. You’ll extend your build pipeline by deploying jobs for different environments. Before we can dive into the details of deploying software, let’s review the tools that are helpful for provisioning an infrastructure.
Nowadays, we see a paradigm shift toward cloud provisioning of infrastructure. Unlike the traditional approach, a cloud provider often allocates preconfigured hardware in the form of virtual servers. Server virtualization is the partitioning of a physical server into smaller virtual servers to help maximize the server resources. Depending on the service offer, the operating system and software components are managed by the cloud provider.