Closed maiste closed 2 months ago
After some discussion, we will use a custom VM pointing at download.dune.ci.dev
to store the binaries. I will update the PR so we can finally merge it :+1:
After some discussion, we will use a custom VM pointing at
download.dune.ci.dev
to store the binaries. I will update the PR so we can finally merge it 👍
Fantastic, what could also change about generating the HTML file ?
After some discussion, we will use a custom VM pointing at
download.dune.ci.dev
to store the binaries. I will update the PR so we can finally merge it 👍Fantastic, what could also change about generating the HTML file ?
Nothing will change for the HTML generation, as we would still rely on GitHub to deliver the HTML. It's more convenient for us.
@gridbugs @Leonidas-from-XIV : I have set up the secrets on the repository. If that's good for you, I can merge :+1:
Hi :wave:
This PR is in the context of tarides/team-build-system#34 and tarides/team-build-system#41.
This PR is a draft of what the
dune
binary distribution pipeline could look like. The code is in OCaml as I was more efficient at writing it, but it can be rewritten in any other language if needed. Some variables are hard-coded for a test purpose, I intend to move them to environment variables as soon as we agree to keep thisThe goal of this PR is to be able to export our binary to an S3 bucket and generate the HTML to reflect the state of the S3 bucket.
Some improvement that could come if we decide to continue on this path:
toolchains
andmain
, depending on the workflow we choose (here we buildtoolchains
)wget
)From the current estimation, it shouldn't cost that much yearly (less than €10).
Let me know what you think of this solution, I'm open to improvement here! :smile: