From f066aee59806e6123886bd6ace04319bd5f38bf1 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Sat, 2 Sep 2023 11:54:33 +0100 Subject: bitbake: doc: Document challenges of tags with git fetcher Using tags with the git fetcher may cause surprising behaviour. There are reasons for this, document them. (Bitbake rev: 56224da378ab63526d44fd7a70bcfd2cffe245cc) Signed-off-by: Richard Purdie --- bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst index f5723d6767..c905288c48 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst @@ -476,6 +476,14 @@ Here are some example URLs:: easy to share metadata without removing passwords. SSH keys, ``~/.netrc`` and ``~/.ssh/config`` files can be used as alternatives. +Using tags with the git fetcher may cause surprising behaviour. Bitbake needs to +resolve the tag to a specific revision and to do that, it has to connect to and use +the upstream repository. This is because the revision the tags point at can change and +we've seen cases of this happening in well known public repositories. This can mean +many more network connections than expected and recipes may be reparsed at every build. +Source mirrors will also be bypassed as the upstream repository is the only source +of truth to resolve the revision accurately. For these reasons, whilst the fetcher +can support tags, we recommend being specific about revisions in recipes. .. _gitsm-fetcher: -- cgit v1.2.3-54-g00ecf