switch to hercules ci

[zowoq]

No description provided.

[zowoq]

@Mic92 Can I enable hercules for this repo, will it interfere with the current build/release process?

[zimbatm]

This list will need to include the Hercules CI checks

[zimbatm]

Might as well remove the Garnix app from the repo instead

[zowoq]

This is just to save some cycles, I'll drop this and the garnix app can be disabled when we're ready to merge.

[Mic92]

@Mic92 Can I enable hercules for this repo, will it interfere with the current build/release process?

Sure.

[Mic92]

@zowoq Just so you are aware, there are people/customers relying on these assets to be available: https://github.com/nix-community/nixos-images/releases/tag/nixos-unstable so please make sure they don't get accidentally deleted or if they do they are quickly restored.

[zowoq]

It's a bit awkward running the script in an effect so I'll leave that for now.

I'll swap out garnix for hercules and keep the release process in the action.

[zowoq]

I'll pick this up again in the next couple of weeks.

I'll probably rewrite the script as an effect and let hercules create/merge the flake updates to avoid issues with bors, effects have some new features for publishing releases that may be useful as well.

I'll create a fork in this org to work on so I can test publishing releases without disrupting this repo.

[Kranzes]

I have some WIP fork for this, it requires a couple of features to be added to HCI's github releases effect.
https://github.com/Kranzes/nixos-images/
hercules-ci/hercules-ci-effects#132

[zowoq]

I was looking at using the same tag (e.g. artifacts) for both stable and unstable and versioning the files, thought that might be simpler?

gh release delete artifacts
gh release create artifacts --title "build $date" "$files"

bzImage-aarch64-22.11-linux
bzImage-aarch64-unstable-linux
bzImage-x86_64-22.11-linux
bzImage-x86_64-unstable-linux
initrd-aarch64-22.11-linux
initrd-aarch64-unstable-linux
initrd-x86_64-22.11-linux
initrd-x86_64-unstable-linux
netboot-aarch64-22.11-linux.ipxe
netboot-aarch64-unstable-linux.ipxe
netboot-x86_64-22.11-linux.ipxe
netboot-x86_64-unstable-linux.ipxe
nixos-kexec-installer-aarch64-22.11-linux.tar.gz 
nixos-kexec-installer-aarch64-unstable-linux.tar.gz 
nixos-kexec-installer-x86_64-22.11-linux.tar.gz 
nixos-kexec-installer-x86_64-unstable-linux.tar.gz 

[Mic92]

I was looking at using the same tag (e.g. artifacts) for both stable and unstable and versioning the files, thought that might be simpler?

gh release delete artifacts
gh release create artifacts --title "build $date" "$files"

bzImage-aarch64-22.11-linux
bzImage-aarch64-unstable-linux
bzImage-x86_64-22.11-linux
bzImage-x86_64-unstable-linux
initrd-aarch64-22.11-linux
initrd-aarch64-unstable-linux
initrd-x86_64-22.11-linux
initrd-x86_64-unstable-linux
netboot-aarch64-22.11-linux.ipxe
netboot-aarch64-unstable-linux.ipxe
netboot-x86_64-22.11-linux.ipxe
netboot-x86_64-unstable-linux.ipxe
nixos-kexec-installer-aarch64-22.11-linux.tar.gz 
nixos-kexec-installer-aarch64-unstable-linux.tar.gz 
nixos-kexec-installer-x86_64-22.11-linux.tar.gz 
nixos-kexec-installer-x86_64-unstable-linux.tar.gz 

I think I prefer using tags per release. Reason is that I don't want to delete old releases but stop updating them at some point. Also over time we might add/remove images.

[Kranzes]

I agree that seperate releases is the way to go, someone just needs to implement the missing features to the HCI effect.

[zowoq]

@Kranzes Do you want to take this over?

[Kranzes]

@Kranzes Do you want to take this over?

Sure, I mean I've already done most of the work needed (see my fork). Only thing missing some some changes to HCI.