Add CI/CD pipelines and deb/rpm packaging options #41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's included
dpkg -i
and the rpm equivalent. No additional dependency besidesgoreleaser
is necessary for local development. The packages will install the binary in/usr/local/bin
by default (see https://goreleaser.com/customization/#NFPM)dist
Why
What you need to do before merging
Set up signing key
gpg --quick-generate-key helm-docs default default never
(Do NOT use your personal private key!)gpg --list-keys
, the id looks likeE57761BCB035C49A7068EF97083880A377733DD7
gpg --armor --export-secret-key E57761BCB035C49A7068EF97083880A377733DD7
SIGNING_KEY
in https://github.com/norwoodj/helm-docs/settings/secrets (it begins with-----BEGIN PGP PRIVATE KEY BLOCK-----
)gpg --armor --export E57761BCB035C49A7068EF97083880A377733DD7 > signature.asc
) somewhere in this Repo, e.g..github/signature.asc
or in the project root dir, file name/extension also doesn't matter, it's just a proposal. So that users can verify the downloads with the public key..goreleaser.yml
:(or you can do it directly in your own commit, I don't mind)
This only takes around 15min to do ;)
Set up CI/CD
DOCKER_HUB_USER
in https://github.com/norwoodj/helm-docs/settings/secrets (it's probably jnorwood like your Docker Hub repo, but for good measure, should it change somehow)DOCKER_HUB_PASSWORD
in the secrets(Note: Secrets do NOT get passed to PR builds or printed in CI output, so your Docker Hub access isn't leaked.)