This message was deleted.

Does this help? https://docs.gradle.org/current/userguide/declaring_repositories.html#sec:handling_credentials

the easiest way is to pass them in the environment. setting

ORG_GRADLE_PROJECT_mypassword=

behaves like adding

-Pmypassword=

to the Gradle command or as a Gradle property

This answer is related: https://stackoverflow.com/questions/72058462/gradle-version-catalog-published-how-to-dynamically-set-up-repository/72075210#72075210

and yes, if the password is for a maven repository or something else that uses Gradle's credentials support, do that.

Those are useful links and some of which I've seen, but it all seems to boil back down to "pass it via environment variable". Which means my password is exposed in the environment vars. I feel like none of these solutions consider how CI systems actually behave. I wanted to just be able to give it a secure path to a securely stored properties file. I do this with maven currently, I pass in -Dsettings or whatever to settings.xml

CI systems all support a way to pass environment variables without displaying them in the logs

Hm yes you are correct, checking the Azure pipelines docs. Thank you I'll give that a shot