I guess I'm not submitting new versions of my pers...
# announcements
s
I guess I'm not submitting new versions of my personal libs for a while, given that Maven Central requires signing files, and signing within GitLab CI is just begging for someone to steal the keys. Hopefully someone builds an alternative soon.
n
an alternative to requiring signing artifacts?
s
An alternative to JCenter.
n
jitpack is about as scrappy as it comes, might be relevant
v
JitPack is a real PITA, broken by design and unreliable as hell. It's not a real alternative to proper publishing.
1
e
gitlab ci supports secrets - variables can only be seen by maintainers
n
I think Campbell was worried about someone hacking GitLab or their hardware
s
indeed it does, but I'd rather not shove an entire gnupg configuration through an environment variable
Maven signing needs access to the keyring, if I'm not mistaken
e
and do what, perform rogue uploads to central? they'd have to hack that too, and you're in the same boat with jcenter/bintray
s
I can't envision a reasonable way to pack up an entire gnupg configuration, keyring and all, into an environment variable
At least JCenter let me get around that by mirroring to Maven Central and signing the files with their own key, but clearly that isn't an option anymore
e
encrypted keyring in storage (aws or whatever), secret api key and passphrase
or put the whole key into a variable, apparently it fits fine. https://frank.sauerburger.io/2018/07/25/sign-ci-artifacts.html
s
image.png
e
right, so just
echo "${SECRET_KEY}" | gpg --import
before your build like https://gitlab.sauerburger.com/frank/sign-in-ci demonstrates
s
noted, thanks
s
yeah, i used CI env vars for my bintray key already
this works fine