You can use Properties Configuration Task to substitute variables "${variable}" placeholders in config files with environment specific values for deployment/build. from plan variables and override files. Variables are source from plan variables (e.g. ${bamboo.buildResultKey}) and optionally an external override file
| Info | ||
|---|---|---|
| ||
This task is available after installing the DataMigrators - Bamboo Properties Configuration Plugin (dm-bamboo-properties-config-plugin-<version>.jar) |
...
- Navigate to the Tasks configuration tab for the job (this will be the default job if creating a new plan).
- Click the name of an existing Properties Configuration Task, or click Add Task and then search 'Properties Configuration' to easily locate the Properties Configuration Task type, in order to create a new task.
Complete the following settings:
Task Description A description of the task, which is displayed in Bamboo. Disable this task Check, or clear, to selectively run this task. Base Directory Optional: A relative path from the working directory to the root directory of configuration file(s). This path will be the root of file patterns.
If not specified, the agent working directory will be used
File Patterns Relative paths to different configuration files from the base directory (wild card is acceptable). Each line is one pattern.
Examples:
*.apt
DSParams
Parameter Sets/*/*Override File Optional: A relative path from the working directory to
the override file, which isa Java properties file
. This file must contains all variables' values.containing variable values to be used during substitution.
Output Directory Optional: A relative path from working directory to write all filled configuration files to (all relative path from the base directory will be preserved. If output directory is the same as base directory, all original configuration files will be replaced.
If not specified, the agent working directory will be used
- Click Save
