You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Michael Bridgen 7ae4f28920 Use a file to record successful manifests build ... Using the directory cmd/flux/manifests as a prerequisite causes a problem: if the script that creates the files within fails, the next invocation of make will see the directory and assume it succeeded. Since the executable expects certain files to be present, but they are not explicit prerequisites of the recipe for building the binary, this results in a successful build but a broken `flux` executable. Instead, depend on a file that's explicitly updated when the script has succeeded, and which itself depends on the inputs. A couple of the CI workflows run make cmd/flux/manifests before doing other things, presumably as a way to avoid running the whole test suite in a CI pipeline for some purpose other than testing, so these needed changing as well. Signed-off-by: Michael Bridgen <michael@weave.works>		4 years ago
..
bootstrap.yaml	Use a file to record successful manifests build	4 years ago
e2e-arm64.yaml	Move arm64 e2e to Go tests	4 years ago
e2e.yaml	Add image scanning e2e tests	4 years ago
rebase.yaml	Align formatting and extensions workflows	5 years ago
release.yaml	Generate OpenAPI schema in CI	5 years ago
scan.yaml	Use a file to record successful manifests build	4 years ago
update.yaml	build: tidy after go mod edit	5 years ago