Table of Contents

Search

  1. Preface
  2. Informatica Developer
  3. The Model Repository
  4. Searches in Informatica Developer
  5. Connections
  6. Physical Data Objects
  7. Flat File Data Objects
  8. Logical View of Data
  9. Viewing Data
  10. Application Deployment
  11. Application Patch Deployment
  12. Application Patch Deployment Example
  13. Continuous Integration and Continuous Delivery (CI/CD)
  14. Object Import and Export
  15. Appendix A: Data Type Reference
  16. Appendix B: Keyboard Shortcuts
  17. Appendix C: Connection Properties

Developer Tool Guide

Developer Tool Guide

Continuous Delivery

Continuous Delivery

As objects pass testing in the development environment, the objects are continuously delivered to the production environment. Based on organizational requirements, you can set up continuous delivery to additional environments, such as QA and UAT, before delivering the objects to the production environment.
To simplify continuous delivery, you can use archive files to create consistency between the objects that were tested and approved in the development environment and the objects that are delivered to additional environments. To create consistency, set up continuous delivery to deploy objects to one archive file, store the archive file in a version control system, and deploy the archive file to each environment.
The following image shows how one application patch archive file can be deployed to development, QA, UAT, and production environments:
You use the objects in the Model repository to create an archive file. You store the archive file in a version control system. You access the archive file in the version control system and deploy the archive file to the development, QA, UAT, and production environments.
  1. Objects are deployed to an application patch archive file.
  2. The archive file is stored in a version control system.
  3. The same archive file is deployed to development, QA, UAT, and production environments.

0 COMMENTS

We’d like to hear from you!