Add workflow to test building changed recipes - #121
Open
igorauad wants to merge 1 commit into
Open
Conversation
Open
Build the recipes that were changed only to restrict the scope.
2 tasks
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
1 participant
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.
It would be nice to have a workflow to test whether new/updated recipes build successfully. This PR adds a workflow I have been experimenting with to test a new recipe (gr-dvbs2rx, pushed in another PR).
The current implementation is still based on the igorfreire/pybombs-dev image on my DockerHub account. However, I also plan on moving this image and the OOT dev image I maintain into the gnuradio workspace, as discussed here: gnuradio/gnuradio#6194.
I have tested the given implementation on push events. The job will process the
.lwrfiles changed relative to the master branch and callpybombs installon them. My next step is to test whether the job is functional on PRs. So the roadmap for this PR is as follows:igorfreire/pybombs-devis moved intognuradio/pybombs-dev.