On Mon, Sep 30, 2019 at 10:26:54PM +0530, Lakshmipathi.G wrote: > Make use of GitLab-CI nested virutal environment to start QEMU instance > inside containers > and perform btrfs-progs build, execute unit test cases and save the logs.
This looks good, thanks! > More details can be found at https://github.com/kdave/btrfs-progs/issues/171 > > Signed-off-by: Lakshmipathi.G <lakshmipathi.ganapa...@collabora.com> > --- > .gitlab-ci.yml | 181 > ++++++++++++++++++++++++++++++++++ > gitlab-ci/Dockerfile | 3 + > gitlab-ci/btrfs-progs-tests.service | 13 +++ > gitlab-ci/build_or_run_btrfs-progs.sh | 37 +++++++ > gitlab-ci/kernel_build.sh | 30 ++++++ > gitlab-ci/run_tests.sh | 9 ++ > gitlab-ci/setup_image.sh | 42 ++++++++ Is it possible to move the files to ci/gitlab? .gitlab-ci.yml must be probably in the top-level dir but that's acceptable. > 7 files changed, 315 insertions(+) > create mode 100644 .gitlab-ci.yml > create mode 100644 gitlab-ci/Dockerfile > create mode 100644 gitlab-ci/btrfs-progs-tests.service > create mode 100755 gitlab-ci/build_or_run_btrfs-progs.sh > create mode 100755 gitlab-ci/kernel_build.sh > create mode 100755 gitlab-ci/run_tests.sh > create mode 100755 gitlab-ci/setup_image.sh The scripts look good to me but I have limited knowledge of the CI environment so I don't have objections against merging the patch. I'll spend some time experimenting but overall this seems in a good shape and we'll get further coverage (due to the new kernel) than what travis provides. Thanks.
