Gradle Pass Configuration on Command Line: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 23: Line 23:
ext {
ext {
     myEnvironmentDependentConfig = System.getProperty("my.environment.dependent.config", "red");
     myEnvironmentDependentConfig = System.getProperty("my.environment.dependent.config", "red");
}
</syntaxhighlight>
The value can be access as such:
<syntaxhighlight lang='groovy'>
task displayPropertyValueAtExecutionTime {
    doLast {
        println "myEnvironmentDependentConfig: " + myEnvironmentDependentConfig
    }
}
}
</syntaxhighlight>
</syntaxhighlight>

Revision as of 20:33, 20 March 2019

Internal

Overview

It is sometimes necessary to pass environment-specific configuration to the build. An example is the URL of a container registry, which may different values relative to the environment the build is executed. The best place for such configuration is not build.gradle, as we would like to avoid editing it for each environment the build is supposed to execute in. One option, which works well for build containers, is to use custom environment variables. Another option is to use command line-specified system properties, as shown below:

gradle -Dmy.environment.dependent.config=blue ...

If not provided on command line, those configuration elements can always fall back to build.gradle hardcoded values.

Playground

n

Implementation

We assign the value of the system property to a project extra property, for convenient handling:

ext {
    myEnvironmentDependentConfig = System.getProperty("my.environment.dependent.config", "red");
}

The value can be access as such:

task displayPropertyValueAtExecutionTime {
    doLast {
        println "myEnvironmentDependentConfig: " + myEnvironmentDependentConfig
    }
}