You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15-5Lines changed: 15 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,13 +43,23 @@ You can also configure the task itself to specify any of the information set in
43
43
### Github Secrets
44
44
A large motivation for this was wanting to use Github Actions and still be able to sign my built files. Github does not allow you to have files as [secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets) just strings and the workarounds I found involved committing a encrypted form of your keystore to your repo and then decrypting it during an Action. Instead I decided to allow you to specify the keystore file as a base64 encoded string which can be used as a Secret.
45
45
46
-
You can either manually configure the information by pulling the secrets yourself, or I added a simple helper `jarSigner.fromEnvironmentVariables()` which does the following:
46
+
You can either manually configure the information by pulling the secrets yourself, or I added a simple helper `jarSigner.autoDetect()` which which search the following locations in order:
47
+
48
+
if (prefix != null) {
49
+
project.findProperty(prefix + '.' + prop)
50
+
System.getenv(prefix + '.' + prop)
51
+
}
52
+
project.findProperty(prop)
53
+
System.getenv(prop)
54
+
`prefix` defaults to `project.name` you can override by calling `jarSigner.autoDetect('prefix')`
0 commit comments