Pipeline Variables
Your build process may depend upon specific configuration variables which would be inappropriate to place in the git repository or you may need to vary them between pipeline executions using the same branch.Cloud Manager allows for these variables to be configured through the Cloud Manager API or Cloud Manager CLI on a per-pipeline basis. Variables may be stored as either plain text or encrypted at rest. In either case, variables are made available inside the build environment as an environment variable which can then be referenced from inside the pom.xml file or other build scripts.
Uses example
- Used to vary behavior of build process
- Accessible inside the build process
- Dev minification is set differently on Dev vs Stage or Prod
- Disable caching on Dev
Standard Environment Variables
Changing application behavior based on standard environment variables
Uses example:
- Provided to the runtime environment
- Used in OSGi configuration
- Store passwords outside of version control, instead use a reference.
- Connect your AEM application with different external endpoints
Types of environment variables
- Inline values. e.g. { "keyName" : "jorvee" }
- Environment specific values. e.g. { "endpoint" : "$[env:JORVEE_ENDPOINT]" }
- Environment secrets. e.g. { "authToken" : "$[secret:J_AUTH_TOKEN]" }
Variable naming conventions
- Variable names must observe the following conventions.
- Variables may only contain alphanumeric characters and the underscore (_).
- The names should be all upper-case.
- There is a limit of 200 variables per pipeline.
- Each name must be less than 100 characters.
- Each string variable value must be less than 2048 characters.
- Each secretString type variable value must be less than 500 characters.