Feature 2020 run sonarqube

[hsoh-u]

Expected Differences

• Do these changes introduce new tools, command line arguments, or configuration file options? [No]
  
  If yes, please describe:
  

• Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [No]
  
  If yes, please describe:
  

Pull Request Testing

• Describe testing already performed for these changes:
  

  • Configured the crontab under "met_test"account
  • Run the SonarQube scanning nightly
  • Checkout feature_2020_run_sonarqube branch
  • run <MET_checkout_dir>/scripts/sonarqube/run_nightly.sh develop
    • MET code will be downloaded at /d1/projects/MET/MET_regression/sonarqube/NB<YYYYMMDD>/MET-develop
    • And scan the code
    • The scanning result is available at http://mandan:9000/dashboard?id=org.sonarqube%3AMET_NB

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  

Check the daily scanning result at http://mandan.rap.ucar.edu:9000/dashboard?id=org.sonarqube%3AMET_NB

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes or No]

• Do these changes include sufficient testing updates? [No]

• Will this PR result in changes to the test suite? [No]
  
  If yes, describe the new output and/or changes to the existing output:
  

• Please complete this pull request review by [Fill in date].
  

Pull Request Checklist

See the METplus Workflow for details.

• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Define the PR metadata, as permissions allow.
  Select: Reviewer(s)
  Select: Organization level software support Project or Repository level development cycle Project
  Select: Milestone as the version that will include these changes
• After submitting the PR, select Linked issues with the original issue number.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.

[JohnHalleyGotway]

I approve of these changes. I see this adds logic to run SonarQube on seneca. I see the results displayed at http://mandan.rap.ucar.edu:9000/dashboard?id=org.sonarqube%3AMET_develop_NB. Looks to me like its working! Thanks.