Multiple repository set, repository with credentials in Gradle

I really like the idea behind this gradle plugin, however I found the settings thin too.

Actually there is a gradle repo for the co-workers in our company, but this repo is only reachable with credential data. There are stored the common libs. So my gradle file looks like this:

repositories {
    mavenCentral()
    maven { url "https://repo.spring.io/snapshot" }
    maven { url "https://repo.spring.io/milestone" }
    maven {
        url "https://...."
        credentials {
            username = "${readerJfrogUser}"
            password = "${readerJfrogUserPw}"
        }
    }
}

Its working fine If I build my stuff the original way, however, I can not set multiple repo url, and credentials (for them) in the settings section.

Can it be a future feature? Or has somebody any workaround ?

[dsyer]

We seem to have veered off topic from the original issue though, or am I missing something? The original topic was about custom repositories with credentials. It wasn’t anything to do with multistage docker builds and optimization of docker caches.

All you need to make it work is a Maven settings.xml with the repository credentials. You have to figure out a way to inject the secrets from environment variables, but I know it’s possible (plenty of docs if you google), and you already have that problem with the build.gradle, so you must have solved it somehow.

[GergelyLakatos]

Okey, let me explain. We dont have this cache option, because our build system is not an usual one.

Dockerfile looks like this:

FROM openjdk:11-jre-slim AS base
WORKDIR /app


FROM gradle:5.5.1-jdk11 AS build
COPY . /src
WORKDIR /src
RUN ["gradle", "clean", "build", "-PexcludeRepoTests"]


FROM base AS final
COPY --from=build /src/build/libs/myapp* /app/myapp.jar
ENTRYPOINT ["java", "-jar", "/app/myapp.jar"]

So we have no gradle cache in the jenkins (build) server, because we use a docker image for build (gradle:5.5.1-jdk11), and an another one for run it (openjdk:11-jre-slim). Our jenkins is abstract, and it handles nothing but docker build, and deploy.

So (with your solution), I have to make an automation, for making a builder docker image what would contain all the dependencies what it need for the build, and it should be changed as the deps changes… Its complicated.

My goal was a Dockerfile like this:

FROM openjdk:11-jre-slim AS base
WORKDIR /app


FROM gradle:5.5.1-jdk11 AS build
COPY . /src
WORKDIR /src
RUN ["gradle", "clean", "buildonlydependencies"] # it makes the jar of dependencies
RUN ["gradle", "clean", "buildcore", "-PexcludeRepoTests"] # it makes the core jar and runs the tests


FROM base AS final
COPY --from=build /src/build/libs/myapp* /app/myapp.jar
ENTRYPOINT ["java", "-jar", "/app/myapp.jar"]

And why is it good for me? Because if a gradle command like buildonlydependencies would exist, the docker would handle it so well, because it can make a cache layer from it, so that step would come from the docker cache (if the deps does not change), and most of the time the build process should focus only the core.jar.

I hope you can understand now.