Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
CI: allow to override the kdevops-results-archive ref used
The kdevops-results-archive will have a commit log which describes the trigger tree used to create the test and then also the ref used. kdevops can be used for CI with two setups: a) Using something like kernel-patch-daemon which creates a series of patches from patchwork and then pushes onto a tree under the linux-kdevops organization. The way kpd does this is it first merges the respective CI files so the .github directory and then applies the patches. The last patch is what we use right now for the commit log subject we use for committing the archive into the kdevops-results-archive. The last commit in this case would make sense, and the ref is ephemeral as its just a patch on the mailing list. 2) A kernel maintainer will use an existing tree but want to trigger at test. In this case it makes sense for a kernel maintainer to want to keep the git history and so the .github directory would be added at the very end. In this case, it makes no sense to have a commit log on kdevops-results-archive which mentions the last commit which just adds the .github directory. We can special case and test for this on the github actions and have it just add an optional file which can override the default ref used on the kdevops-results-archive repo. This allows us to also use this ref for the zip archive, and so for example, if we are testing the Linux kernel official refs we will upkeep the ref and be able to keep the archive file with the name as well. So this adds support for 2) as an option. Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
- Loading branch information