NOTE: Given the personal and private nature of these values, a good practice is to store them in the `gradle.properties` file in the user's Gradle home directory (described in <<build_environment.adoc#sec:gradle_system_properties,System properties>>) instead of in the project directory itself.

[source,properties]
----
signing.keyId=24875D73
signing.password=secret

* Task output property names
* Individual task property input hashes
* Hashes of files which are part of task input properties

If you want information about the build cache key and individual input property hashes, use <<build_environment.adoc#sec:gradle_configuration_properties,`-Dorg.gradle.caching.debug=true`>>:

[listing]
----
$ ./gradlew :compileJava --build-cache -Dorg.gradle.caching.debug=true

.
.
.

                    </ul>
                </li>
                <li><a href="../userguide/directory_layout.html">Gradle-managed Directories</a></li>
                <li><a href="../userguide/build_environment.html">Configuring the Build Environment</a></li>
                <li><a href="../userguide/logging.html">Logging with Gradle</a></li>
            </ul>

w: build.gradle.kts:4:5: 'getter for uploadTaskName: String!' is deprecated. Deprecated in Java
----

It is possible to configure your build to fail on any warning emitted during script compilation by <<build_environment#sec:gradle_configuration_properties,setting>> the `org.gradle.kotlin.dsl.allWarningsAsErrors` Gradle property to `true`:

[source,properties]
----
# gradle.properties
org.gradle.kotlin.dsl.allWarningsAsErrors=true

that allows you to declare only the type of required credentials. Credential values are looked up from the <<build_environment.adoc#sec:gradle_configuration_properties,Gradle Properties>>
during the build that requires them.

For example, given repository configuration:

.Externalized repository credentials
====

* settings file in the root of the build
* build file in the root of each subproject

For the use case where custom settings or build files are used to model different behavior (similar to Maven profiles), consider using <<build_environment#sec:gradle_system_properties, system properties>> with conditional logic.
For example, given a piece of code in either settings or build file:
```
if (System.getProperty("profile") == "custom") {