abroekhuis commented on a change in pull request #263: URL: https://github.com/apache/celix/pull/263#discussion_r447244695
########## File path: .github/workflows/coverity-scan.yml ########## @@ -0,0 +1,56 @@ +name: coverity-scan +on: + schedule: + - cron: '0 0 * * 0' # Weekly at 00:00 UTC + +jobs: + latest: + runs-on: ubuntu-18.04 + steps: + - name: Checkout source code + uses: actions/checkout@master + - name: Install dependencies + run: | + sudo apt-get update + sudo apt-get install -yq --no-install-recommends \ + build-essential \ + curl \ + uuid-dev \ + libjansson-dev \ + libcurl4-openssl-dev \ + default-jdk \ + cmake \ + libffi-dev \ + libxml2-dev \ + libczmq-dev \ + libcpputest-dev + - name: Download Coverity Build Tool + run: | + mkdir -p build/cov-analysis-linux64 + cd build + wget -q https://scan.coverity.com/download/cxx/linux64 --post-data "token=$TOKEN&project=Apache+Celix" -O cov-analysis-linux64.tar.gz + tar xzf cov-analysis-linux64.tar.gz --strip 1 -C cov-analysis-linux64 + env: + TOKEN: ${{ secrets.COVERITY_SCAN_TOKEN }} + - name: Build + env: + BUILD_OPTIONS: | + -DENABLE_TESTING=ON + -DCMAKE_BUILD_TYPE=Debug + run: | + cd build + cmake ${BUILD_OPTIONS} .. + export PATH=`pwd`/cov-analysis-linux64/bin:$PATH + cov-build --dir cov-int make + - name: Submit the result to Coverity Scan + run: | + tar czvf celix.tgz cov-int +# curl \ +# --form project=Apache+Celix \ +# --form token=$TOKEN \ +# --form [email protected] \ Review comment: I would want to wait with it even a bit longer, to be able to test the flow without impacting the scan limit coverity has. The token is needed to download the cov tools as well, so I'm not going to merge this until infra is done. Regarding the mailadres, I suspect it is coupled to the token, looking at the example url coverity shows, it has to be my address. We can try with another address though, and just see what happens. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
