Automatically build and publish development packages (deb/rpm) on merge #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This set of changes, including three github actions workflows, and a couple of build scripts and some minor changes on the build server (aptly API, addition of a user that allows writing files to the repo, but not doing other stuff the build user can do, and a publish cronjob for RPMs), and some github secrets (aptly API user/pass, and SSH key and user for RPMs), makes any merge to the
masterbranch builddevelpackages and publish them to the new devel repository.Once this is merged, I'll make a stable branch, and duplicate all the functionality over for building and publishing stable packages as well.
I need to add more secrets to the virtualmin/webmin-jailkit github repo, so this shouldn't be merged for a few more minutes...but, I think it's all working and ready to go.
It also runs any tests in
tusingprove. If anyone writes more unit or functional tests, that'd be great. Most modules only have a Strict test.