Skip to content
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

Idea: upload binaries from CI runs #5

Open
hannesm opened this issue Oct 21, 2024 · 2 comments
Open

Idea: upload binaries from CI runs #5

hannesm opened this issue Oct 21, 2024 · 2 comments

Comments

@hannesm
Copy link
Contributor

hannesm commented Oct 21, 2024

We use cirrus CI a lot to build our unikernels. We should there use orb and upload the results to builder-web.

For builder-web, I suspect it'd be good to have Bearer authentication in place.

For the cirrus jobs, we'll need to store the secrets somewhere (and figure out how to do so). Also, we will need to use orb to build the package (and eventually builder for packing it up), and then uploading it to builds.robur.coop.

@reynir
Copy link
Contributor

reynir commented Oct 21, 2024

Hmm. I guess in order to build unikernels we would need to run mirage configure first to get an opam file that we can feed to orb? And then somehow orb needs to know how to get the source. I think it is an interesting idea, and worth exploring.

@hannesm
Copy link
Contributor Author

hannesm commented Oct 21, 2024

right. maybe we would need to tweak orb so it runs the mirage configure or we'd do a multi-step approach, and first install mirage and then later orb. given that we can run orb with an existing opam switch (or at least there was a time where we were able to - we may need to reactivate this), I guess that's fine. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants