SpringCloud/spring-cloud-contract
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fixes #1672: allow users to specify a custom build.gradle when using standalone docker image (#1695)

Browse Source 
* pre-create directories for mounting and use /spring/cloud-contract and /contract and /spring-cloud-contract

* add documentation on how to run a customized gradle build to create tests
This commit is contained in:
Bastian Doetsch
2021-08-10 15:59:32 +02:00
committed by GitHub
parent 9b147dd991
commit 2f37b46dde
4 changed files with 39 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docker/spring-cloud-contract-docker/project/README.adoc
View File

@@ -2,6 +2,7 @@
## Developer tips
### Environment variables
In order to use a new environment variable inside the Gradle script, you need to add it to the `envVars` map together with a description and a default value. Otherwise, any attempt to resolve such an environment variable will lead to an exception being thrown.
If you're referencing any environment variables from inside the Java code please follow the following convention.
@@ -14,4 +15,10 @@ If you're referencing any environment variables from inside the Java code please
String envVar;
```
If you provide Javadocs, we will automatically parse any `@Value` annotated fields and build a table of environment variables with description and default values.
If you provide Javadocs, we will automatically parse any `@Value` annotated fields and build a table of environment variables with description and default values.
### Customizing the gradle build
You can provide a customized `gradle.build` to be run in the container by mounting your customized build file as a volume when running the container:
`docker run -v <absolute-path-of-your-custom-file>:/spring-cloud-contract/build.gradle springcloud/spring-cloud-contract:<version>`