4 commits

Author	SHA1	Message	Date
Graham Christensen	1a30a0c2f1	Dynamic RunCommand: validate that the job's out exists, is a file (or points to a file) which is executable.	2022-02-01 10:57:30 -05:00
Graham Christensen	c2be27e82b	fanout.t: switch to makeAndEvaluateJobset	2022-02-01 10:57:30 -05:00
Graham Christensen	e7f68045f4	DynamicRunCommand: pull out the function determining if a build is ... eligible for execution under dynamic run commands.	2022-02-01 10:57:30 -05:00
Graham Christensen	e56c49333f	RunCommand: Add a WIP execution of dynamic commands ... This in-progress feature will run a dynamically generated set of buildFinished hooks, which must be nested under the `runCommandHook.*` attribute set. This implementation is not very good, with some to-dos: 1. Only run if the build succeeded 2. Verify the output is named $out and that it is an executable file (or a symlink to a file) 3. Require the jobset itself have a flag enabling the feature, since this feature can be a bit dangerous if various people of different trust levels can create the jobs.	2022-02-01 10:57:30 -05:00