diff options
| author | Paulo Neves <paulo@myneves.com> | 2023-02-17 17:00:38 +0000 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2023-02-22 12:03:39 +0000 |
| commit | ffcc20770db8c6d5fcf67d8203b43203a4e7226e (patch) | |
| tree | 790329443eb306354b076fb3ac5eb5c4d15f17b6 /bitbake/lib/bb/fetch2/git.py | |
| parent | 41c86ad30e2faec6ad286b9131578183b6a17d24 (diff) | |
| download | poky-ffcc20770db8c6d5fcf67d8203b43203a4e7226e.tar.gz | |
bitbake: tests/fetch: Add real git lfs tests and decorator
Added tests that verify that git-lfs works with an actual
real git-lfs server. This was not previously the case because
the repo in the test was a simulation of git-lfs but not
a real git lfs repo.
The 2 added tests are almost the same but test that the
git lfs file checkout is successfult with or without the
lfs=1 flag. The lfs=1 URI parameter is a quirk that triggers
2 different code paths for git lfs.
lfs=1, when used on git lfs repositories triggers the git lfs
downloading at the fetch bare stage.
lfs query parameter unset triggers the git lfs downloading only
on checkout as an implicit behavior of git. This leads to possible
network access on the unpack stage and outside the DL_DIR.
lfs=0 actually disables git-lfs functionality even if supported.
(Bitbake rev: d2be7f7f652360f13cd66d0850f3e19ffe2afb0a)
Signed-off-by: Paulo Neves <paulo@myneves.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/fetch2/git.py')
0 files changed, 0 insertions, 0 deletions