Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

toolchains: print git version #8290

Merged
merged 1 commit into from Dec 21, 2017

Conversation

smlng
Copy link
Member

@smlng smlng commented Dec 19, 2017

Contribution description

Minor enhancement to print the GIT version used by the CI, recently found that pkg libcoap patching fails with newer GIT versions, so might be good to know which is used by CI and which one has on their system.

Issues/PRs references

See also #8289

@smlng smlng added Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation Impact: minor The PR is small in size and might only require a quick look of a knowledgeable reviewer CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Area: tools Area: Supplementary tools labels Dec 19, 2017
@smlng smlng added this to the Release 2018.01 milestone Dec 19, 2017
@smlng smlng requested a review from kaspar030 December 19, 2017 14:26
@@ -91,4 +91,5 @@ for p in avr; do
done
printf "%20s: %s\n" "cppcheck" "$(cppcheck_version)"
printf "%20s: %s\n" "coccinelle" "$(spatch_version)"
printf "%20s: %s\n" "git" "$(git --version)"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess we can assume git is always available? If it isn't, would "$(git --version || echo "missing/error")" yield tousable output?

Copy link
Member Author

@smlng smlng Dec 19, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thought about that, too first - but if there is no git you can't clone/checkout RIOT and never call this script right?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Theoretically speaking a user would be able to download a zip file from github and never touch git right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I amended a proper version check as for other tools. Though, I doubt someone would download RIOT as a ZIP and would then call a script that is supposed to be used by CI (only).

@smlng smlng force-pushed the ci/toolchain/print_git_version branch from de6e338 to e18aa35 Compare December 19, 2017 15:19
@smlng
Copy link
Member Author

smlng commented Dec 21, 2017

@kaspar030 and @bergzand: your comments are addressed, do you ACK?

Copy link
Contributor

@kaspar030 kaspar030 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK.

@kaspar030 kaspar030 merged commit 6f99a98 into RIOT-OS:master Dec 21, 2017
@smlng smlng deleted the ci/toolchain/print_git_version branch December 21, 2017 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: tools Area: Supplementary tools CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Impact: minor The PR is small in size and might only require a quick look of a knowledgeable reviewer Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants