Add packages and hydraJobs to flake outputs #17
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user
	
	No description provided.
		
		Delete Branch "abonerib/bscpkgs:hydraJobs"
	
	Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Not sure if having both
packagesandlegacyPackagescan be a problem. So far I have not run into any issues, but I have not tried anything too fancy.I am running a hydra service on weasel (@
weasel:3001) to see if it is any useful. It runs on top of this branch to run thebsc-cithrough hydra and keep the nix store up to date. The main problem I have found with hydra is that it spams the journal logs like crazy...@ -16,0 +29,4 @@(flip getAttrs pkgs)(flip removeAttrs [ "bsc" ])(filterAttrs (_: isDerivation))];I would wait until we have a problem that needs us to use packages, and then we can think how to make this simpler. For now, legacyPackages seems to be enough.
@ -16,0 +32,4 @@];hydraJobs = {inherit (self.legacyPackages.x86_64-linux.bsc-ci) test;s/x86_64-linux/${system}/?@ -16,0 +33,4 @@hydraJobs = {inherit (self.legacyPackages.x86_64-linux.bsc-ci) test;packages = self.packages.${system};Can we just use
self.legacyPackages.${system}.bsc-ci.pkgs? If you want to have package granularity, we could expose the bscPkgs package set in bsc-ci, then use that attribute here. I would rename the current bsc-ci.pkgs to bsc-ci.pkgsList and use bsc-ci.pkgs as the bscPkgs, so it is less confusing.6491ba90adtoe07d9f21dce07d9f21dcto2ffdd53d86