vyos/vyos-build
1
0
Fork 0
mirror of https://github.com/vyos/vyos-build.git synced 2025-10-01 20:28:40 +02:00
Code Issues Packages Projects Releases Wiki Activity

T7576: Remove unnecessary code for checking dirty build status

Browse Source 
```
vyos@r15:~$ show version | match dir
Build commit ID:  d8038ded37fadb-dirty
```
Having uncommited files in vyos-build is completely normal:
custom configs, EULA files in official release builds,
anything else that flavor files may include.

However, many people are not familiar with the specific
meaning of "dirty" in git or with the build process and assume
that "dirty" means something went wrong with the image build.
This commit is contained in:
Oleksandr Kuchmystyi 2025-07-22 13:05:38 +03:00
parent 28147b4586
commit 71ade9dce3
No known key found for this signature in database
GPG Key ID: 4813EA2FAD6625CC
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
scripts/image-build/build-vyos-image
View File

@ -409,9 +409,6 @@ if __name__ == "__main__":
repo = git.Repo('.', search_parent_directories=True)
# Retrieve the Git commit ID of the repository, 14 charaters will be sufficient
build_git = repo.head.object.hexsha[:14]
# If somone played around with the source tree and the build is "dirty", mark it
if repo.is_dirty():
build_git += "-dirty"
# Retrieve git branch name or current tag
# Building a tagged release might leave us checking out a git tag that is not the tip of a named branch (detached HEAD)