Change Tracking

Change Tracking is designed to track every change between every state of non-runtime CloudBees Flow objects and to allow you to revert to any previous state of these objects. CloudBees Flow tracks the changes to tracked objects including applications or microservices, procedures, workflows, workspaces, resources, and project-owned components such as library components and records a Change History of the historical states of the system and the changes between them. The change history has a copy of every state in which every non-runtime object has been, the object’s current state, and indexing records for searching through the database. The tracked objects are not affected when CloudBees Flow executes an object that is usually created or modified at execution time, such as a workflow or process.

Change tracking allows you to do the following:

  • When debugging a failed job or looking for more information about a component in a CloudBees Flow, see the Change History for the changes relevant to that object.

  • When searching for specific change history records, filter the records by time frame, change type, entity type, or developer.

  • Revert changes to an object or to an objects and its children.

  • When you want to determine the differences between objects, export them at various levels in the object hierarchy.

In CloudBees Flow, you can use Change Tracking in all aspects of the CloudBees Flow end-to-end solution:

  • In build-test automation, track the Change History of artifacts, resources, and ACLs.

  • In deployment automation, track the Change History of components, environment tiers, and process steps (application, microservice, or component). You also use Change Tracking with snapshots to make it easier to deploy reliable and repeatable software for Continuous Delivery.

  • In releases and Pipelines, track the Change History of stages and tasks.

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 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.