- Sweden
- https://mastodon.social/@DataHoarder
-
Loves to tinker with the wrong tools for the job. Also, huge weeb.
- Joined on
2020-10-20
It's live on https://ci.gammaspectra.live/ it'll oauth with this gitea instance.
Once you setup the project I believe I need to make it trusted so it gets built.
I can setup Drone and have it tied with this gitea instance at least, let's give it a go
Oh, there's this message on a mailing list https://releases.nixos.org/nix-dev/2017-June/023903.html
There is also Drone but same points about nix would apply here, from a quick look.
The /nix/ path could be mapped to be shared across most containers, given how nix handles different versions.
I'll attempt to run the demo at least and see how interacts with gitea, and whether…
(and mind you although I have looked into nix, this is the first time I get to use it, so maybe this is well known and a non-issue, I'm learning along the way!)
Thanks for the information, I see the actual symlink now. Going off by https://nixos.org/manual/nix/unstable/command-ref/nix-build.html, it mentions this:
The symlink is called result. If there…
gitea doesn't have a pages-like system, otherwise that would be a solution for presenting such results.
A build status can be set on each commit, and then link to an asset stored somewhere (IPFS?…
Where is the result folder specified on default.nix? Or is this the default output folder
Also, if it can be changed, we could call this results for any other build jobs that generate artifacts in the future.
Shouldn't the build of each part/device be stored under their underlying folder, and then referenced from here?
Also, if it can be changed, we could call this results for any other build jobs that generate artifacts in the future.
I haven't looked into the available build automation platforms as of recently, but worst case it can be done via a webhook that builds for every commit that modifies such files. Or daily builds