Currently, just configuring (not executing) the Gradle build already requires credentials for publishing, as these are evaluated eagerly during configuration phase, see
|
credentials { |
|
username = null == ciOssrhUsername ? null == ossrhUsername ? null : ossrhUsername : ciOssrhUsername |
|
password = null == ciOssrhPassword ? null == ossrhPassword ? null : ossrhPassword : ciOssrhPassword |
|
} |
and
|
credentials { |
|
username = null == ciGHUser ? null == ghUser ? null : ghUser : ciGHUser |
|
password = null == ciGHToken ? null == ghToken ? null : ghToken : ciGHToken |
|
} |
To avoid that, it's probably better to follow the best practice of using the PasswordCredentials class with the built-in mySecureRepositoryUsername / mySecureRepositoryPassword properties.
Currently, just configuring (not executing) the Gradle build already requires credentials for publishing, as these are evaluated eagerly during configuration phase, see
charts/build.gradle
Lines 149 to 152 in 258f877
and
charts/build.gradle
Lines 157 to 160 in 258f877
To avoid that, it's probably better to follow the best practice of using the
PasswordCredentialsclass with the built-inmySecureRepositoryUsername/mySecureRepositoryPasswordproperties.