Hey everyone! How can I access the instance of project in `settings.gradle.kts`? I couldn’t find on...

# gradle

[nuhkoca]

Hey everyone!

How can I access the instance of project in settings.gradle.kts? I couldn’t find one(project) of what I have in root build.gradle.kts

[tapchicoma]

AFAIK you could not access it, the closest what you could access is ProjectDescriptor

[nuhkoca]

I see, thanks. We have a custom properties file in which developers have their own PAT for some repositories. We omit that file in git. Is there any way to read a custom properties file in Settings?

[Vampire]

Why do you actually want to access the project?
It is possible in a delayed way, but my guess is, that you do not actually want / need it.

[tapchicoma]

Is there any way to read a custom properties file in Settings?

You could, like a normal properties file

[Vampire]

For what would you have needed the project for that?

[tapchicoma]

For example:

File versionPropertiesFile = new File(rootProject.projectDir.parentFile, "gradle/versions.properties")
def versionProperties = new Properties()
versionPropertiesFile.withInputStream {
    versionProperties.load(it)
}

[Vampire]

Btw. just in case you are interested, it would have been for example

gradle.rootProject { 
    // do action as soon as project is available, which is after settings evaluation
}

to access the root project, but as I said, just in a delayed fashion.

[Vampire]

Why rootProject.projectDir?
Why not settingsDir ?

[tapchicoma]

yeah, settingsDir will also work

[Vampire]

Well, as long as the settings script is in the root project dir at least

[tapchicoma]

hm, accessing Project via gradle - nice 👍

[Vampire]

But if not, the settings script writer would know as he would have changed that fact.

[tapchicoma]

ah yeah, I've copied this from buildSrc/settings.gradle - in this case it should be rootProject

[nuhkoca]

Thanks to both of you! I’ve fixed it 🙂

[Adam S]

I'm a bit late, but my preference for this is to put settings into $GRADLE_HOME_DIR/gradle.properties and load them using Gradle providers

using providers.gradleProperty("artifactory_password") can be overridden using environment variables too

https://stackoverflow.com/a/72075210/4161471

[nuhkoca]

wow that sounds really cool. So one can put their secrets in global gradle.properties and one line code is enough to retrieve it right?

[Adam S]

yes - also you can override it with a command line arg, or a environment variable (very useful for build servers). Also it's a provider so it's only evaluated if & when it's needed

[nuhkoca]

yes! thanks for the heads-up! Will definitely look into this