Closed MrKevinWeiss closed 4 years ago
Hmm I think this is not what we want. We want to know the env per board. Any hints @smlng?
please separate the changes to the Jenkinsfile into a distinct commit and the script/tooling into another.
Will do but currently it isn't working at all it seems...
Do I need to add a trigger or setups somehow?
I don't know if it could somehow be a separate test since it should be run per node and not on master...
basically okay, but please put scripts into a subdirectory as in RIOT, e.g. dist/tools/ci
and squash too
Squashed and ready to go!
Many thanks!
Description
This PR adds a script to print out the environment variables, python packages being used, and the toolchains being used. It also adds a call for Jenkins to print the information.
Testing Proceedure
Call the
dist/tools/print_versions.sh
from different directories. ~Also read the CI output.~ <- Not included in the CI yet