mirror of
https://github.com/corda/corda.git
synced 2024-12-18 20:47:57 +00:00
6dd33fb8f7
Major changes due to JDK 17: 1. JDK17 JCE Provider now has built-in support for eddsas, corda uses the bouncycastle (i2p) implementation. This PR removes the conflicting algorithms from the built-in JCE provider. 2. JavaScript scripting has been removed from the JDK, the corda log4j config was using scripting to conditionally output additional diagnostic info if the MDC was populated. This PR has removed the scripting. 3. The artifactory plug-ins used are now deprecated, this PR has removed them and uses the same code as Corda 5 for publishing to artifactory. 4. Javadoc generation has been modified to use the latest dokka plug-ins. 5. Gradle 7.6 has implemented an incredibly annoying change where transitive dependencies are not put on the compile classpath, so that they have to be explicitly added as dependencies to projects. 6. Mockito has been updated, which sadly meant that quite a few source files have to changes to use the new (org.mockito.kotlin) package name. This makes this PR appear much larger than it is. 7. A number of tests have been marked as ignored to get a green, broadly they fall into 3 classes. The first is related to crypto keypair tests, it appears some logic in the JDK prefers to use the SunJCE implementation and we prefer to use bouncycastle. I believe this issue can be fixed with better test setup. The second group is related to our use of a method called "uncheckedCast(..)", the purpose of this method was to get rid of the annoying unchecked cast compiler warning that would otherwise exist. It looks like the Kotlin 1.9 compiler type inference differs and at runtime sometimes the type it infers is "Void" which causes an exception at runtime. The simplest solution is to use an explicit cast instead of unchecked cast, Corda 5 have removed unchecked cast from their codebase. The third class are a number of ActiveMQ tests which appear to have a memory leak somewhere. |
||
|---|---|---|
| .. | ||
| src | ||
| build.gradle | ||
| README.md | ||
| test-docker.sh | ||
Building docker images
There are 3 Gradle tasks dedicated to this:
buildDockerFolderwill simply create the build folder with all the dockerfiles and the required artifacts (like thecorda.jar,config-exporter.jar). This is an internal task and doesn't need to be explicitly invoked.buildDockerImagewill build a docker image a publish it in the local docker cachepushDockerImagewill build a docker image and push it to a remote docker registry. It is possible to override the docker registry URL for all images using the--registry-urlcommand-line parameter, otherwise each image will be pushed to its own preconfigured docker registry as specified in thenet.corda.build.docker.DockerImage.destinationfield. The latter field is currently left asnullfor all image variants, which means they are pushed to docker hub.
All 3 tasks use the command-line parameter --image to specify which image variant will be built
(it can be used multiple times to build multiple images).
To get a list of all supported variants simply launch with a random string:
gradlew docker:buildDockerImage --image NON_EXISTENT_IMAGE_VARIANT
results in
> Cannot convert string value 'NON_EXISTENT_IMAGE_VARIANT' to an enum value of type 'ImageVariant' (valid case insensitive values: UBUNTU_ZULU, UBUNTU_ZULU_11, AL_CORRETTO, OFFICIAL)
If no image variant is specified, all available image variants will be built.
The default repository for all images is corda/corda and you will need official R3 credentials
for Artifactory to push there. R3's Artifactory administrators can assist with this if needed,
otherwise you can override the repository name using the docker.image.repository Gradle property.
e.g.
gradlew docker:pushDockerImage -Pdocker.image.repository=MyOwnRepository/test --image OFFICIAL --registry-url registry.hub.docker.com