Question

I'm currently trying to transisiton a maven build to a Gradle build. The show stopper hurdle I've hit is that our internal artifacts are deployed to an internal repository that requires authentication to read.

And you know what authentication means... usernames and passwords. The problem is I don't want to require developers to store their password as plaintext on their hard drives. Maven supports password encryption but I'm not seeing how to make Gradle do it.

Is there some magic access to the Ivy CredentialStore that will support encrypted passwords? or will I have to wait for a new version?

Was it helpful?

Solution

We use Artifactory and Ivy's CredentialsStore works fine.

repositories {
  org.apache.ivy.util.url.CredentialsStore.INSTANCE.addCredentials(REALM, HOST, USER, PASSWORD);
  mavenRepo urls: [ "http://repo.mycompany.com/repo" ]
}

To have each developer use a different username create a gradle.properties file that contains

HOST=repo.mycompany.com
REALM=My Company Realm
USER=theusername
PASSWORD={DESede}xyz123abc

The {DESede} encrypted password prefix may be a Artifactory specific convention.

OTHER TIPS

The gradle-credentials plugin will let you encrypt the contents of a gradle.encrypted.properties file, which will then be available in the build as properties of the credentials object.

The gradle maven settings plugin will let you use Maven's system for encrypting/decrypting credentials.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top