Setup GitHub Actions to build .rpm #27
Open
PWRxPSYCHO wants to merge 26 commits intoTAK-Product-Center:mainfrom
Open
Setup GitHub Actions to build .rpm #27PWRxPSYCHO wants to merge 26 commits intoTAK-Product-Center:mainfrom
PWRxPSYCHO wants to merge 26 commits intoTAK-Product-Center:mainfrom
Conversation
|
I wonder if github is the right place to store binaries. I expect that if I clone this repository I only want source code and no binaries. I build them myself. Just a thought! |
Author
When you clone the repo it won't download the binaries with the project. Setting up GitHub actions just uses GitHub's tools to build the binaries for you. It is also possible to add the binaries to a release similar to what is done currently for the ATAK repository |
|
BTW I had to set |
This file contains hidden or 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
3 participants
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.
These actions build the .rpm image of TAK server and upload them as an artifact to GitHub.
Additional jobs can be added to generate the .deb file as well.
Then a release stage could be created to package the artifacts together.