-
Notifications
You must be signed in to change notification settings - Fork 6k
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
make coverity-scan.sh usable by hand #6747
Conversation
return 0 | ||
} | ||
|
||
if [ "${1}" = "install" ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to use a --with-install
option instead that will just run the install together with the run?
Yep, i need to add a few different combinations of configure options to be tested rather than a single one that we have now. I 'll get to it as soon as we merge this |
if [ -f ".coverity-scan.conf" ] | ||
then | ||
source ".coverity-scan.conf" || exit 1 | ||
fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would probably write it as: [ -f ".coverity-scan.conf" ] && source ".coverity-scan.conf"
, but that may be just matter of personal preference.
Also instead of the exit 1
logic, is better to just set set -e
to enable strict error checking and just use the ||
option for commands we don't want them to stop the process if they fail. what do you think?
BTW we can just merge this and let me take over the rest of the work, but from the commit flow i understand you still working on it |
Taking over as agreed, will come with follow up PR to wrap this up |
* make coverity-scan.sh usable by hand * updated debug variable and docs * merge coverity-scan.sh and coverity-install.sh -- MERGING AND TAKING OVER FURTHER IMPROVEMENTS as agreed --
./coverity-scan.sh
should be easily usable by hand.Prior to this PR, developers should remember to export certain variables (
REPOSITORY
andCOVERITY_SCAN_SUBMIT_MAIL
). They were given to option to configureCOVERITY_SCAN_TOKEN
and configure the path of thecov-build
by configuring separate files for each of them. So, a developer was not able to just configure its environment and then just run the script every time it is needed.This PR allows devs to create the file
.coverity-scan.conf
with the following information:The script is also updated to configure netdata with the following:
Ideally, the script should build all the features of netdata, including:
@paulkatsoulakis I don't know if we should enable these on travis.
Also:
coverity-install.sh
is not needed any more. Run./coverity-scan.sh --with-install
to install coverity build tools. @paulkatsoulakis please update travis and then simply removecoverity-install.sh
from the repo (the update version of this script just calls./coverity-scan.sh install
.functions.sh
is used to simplify the script and beautify the output