-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build ci #8
Conversation
Interesting Interesting! Great stuff! Just wondering, why can't we specify |
@Lex-ari I've put up a PR to the builder fprime-community/project-builder#1. While we're waiting on a review, do you think this is good enough to merge? Using the fprime-community builder in the future is not a big change and we can always add it later. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good!
* Add initial CI build * Archive the uf2 * Add build badge in README * Declare python version and cache pip packages * Upgrade checkout action to remove deprecation notice and rename artifact
* Add initial CI build * Archive the uf2 * Add build badge in README * Declare python version and cache pip packages * Upgrade checkout action to remove deprecation notice and rename artifact
This PR adds an automated build pipeline that publishes the UF2.
We should consider adding pipelines that publish the GDS binary for each major OS.
As I mentioned in the issue, I had intended to use the composite action from the fprime-community builder but I quickly realized that I would be unable to specify the
rpipico
build target (unless I'm missing something?). It's OK though, replacing the composite action only adds a single step.Satisfies #5.