Deployment Automation

CloudBees Flow uses a “model driven” approach to abstract the application or microservice architecture from the environment, infrastructure details so that the same application or microservice can be deployed to many environments using parameterized processes. CloudBees Flow supports the creation, versioning, deployment, required middleware, and infrastructure details for a complete release package. You can model and version applications, microservices, and environments to orchestrate the software release flow and also to standardize and automate the deployment of applications or microservices between environments.

CloudBees Flow Deploy makes deployments manageable, reproducible, and error-proof by modeling the application or microservice, the environments to which it will be deployed, and automating the workflow needed for the deployment. The model can be broken into these parts of your application or microservice deployment:

  1. What—You are deploying the application or microservice, which contains references to the files being deployed.

  2. Where—The application or microservice will be deployed to a CloudBees Flow environment.

  3. How—You run processes that orchestrate deployment tasks to deploy the application or microservice to the environment.

Copyright © 2010-2020 CloudBees, Inc.Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc. Most CloudBees products are commonly referred to by their short names — Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake — throughout various types of CloudBees product-specific documentation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at www.cloudbees.com/jenkins/about. Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.