Overview of Properties

Effective utilization of Properties is important in getting the most out of UrbanCode Deploy.  Property references are replaced with the associated property value.

Properties can be predefined for a context. For example, you can define properties for an Application, Environment, Agent, Component, Resource and so on. To continue the example, if you refer to an Environment Property, a DEV environment can (and generally will) have a different value than a UAT environment.

In addition, properties can be dynamically calculated and assigned. A common example is a process which deploys an EAR file, but the filename is dynamic and includes version information, such as SampleApp_123_12.ear. You can write a Groovy script that dynamically figures out the actual ear filename and puts it into a UCD Property.