Commits on Source (3)
-
Valentin David authored
Instead of tag information being fetched which can change with time, they are tracked and saved in the projects.refs/.bst. Then we re-tag automatically the closest tag so that `git describe` works and is reproducible. This new feature is opt-in with the new `track-tags` configuration, and must be used to fix modules which are broken by our new policy of omitting the `.git/` repository when staging git sources. This fixes issue #487
-
Valentin David authored
-
Tristan Van Berkom authored
Track of git tags and save them to reproduce minimum shallow repository Closes #487 See merge request !906
Showing
- NEWS 4 additions, 0 deletionsNEWS
- buildstream/_versions.py 1 addition, 1 deletionbuildstream/_versions.py
- buildstream/plugins/sources/git.py 203 additions, 13 deletionsbuildstream/plugins/sources/git.py
- tests/cachekey/project/sources/git3.bst 12 additions, 0 deletionstests/cachekey/project/sources/git3.bst
- tests/cachekey/project/sources/git3.expected 1 addition, 0 deletionstests/cachekey/project/sources/git3.expected
- tests/cachekey/project/target.bst 1 addition, 0 deletionstests/cachekey/project/target.bst
- tests/cachekey/project/target.expected 1 addition, 1 deletiontests/cachekey/project/target.expected
- tests/sources/git.py 153 additions, 0 deletionstests/sources/git.py
- tests/testutils/repo/git.py 14 additions, 0 deletionstests/testutils/repo/git.py
tests/cachekey/project/sources/git3.bst
0 → 100644
tests/cachekey/project/sources/git3.expected
0 → 100644