swellaby / azure-pipelines-templates Goto Github PK

AZP has changed the way code coverage results are published, which is now resulting in our step template causing warnings. Let's update the coverage upload step to exclude the extra directory param

Create a combo template driven off of invoke steps for basic setup, dependency installation, lint, format check, and to run tests and publish results

Add step template for running cargo audit (https://github.com/RustSec/cargo-audit) to scan for security vulnerabilities

https://github.com/wraithan/cargo-bump

Create Azure Pipelines job to run a CI job on the master branch when there are changes under the /templates directory to create and publish a tag and release in the repo

Sonar is flagging the tests for the test result and code coverage publish steps as duplicates between the two node combo templates.

Probably worth investigating the feasibility of encapsulating this somewhere and/or trying to have Sonar ignore since this isn't really "duplicated" code:

The combo templates utilize many of the same step templates so there's a lot of commonality in the tests for those combo templates.

This is a false positive in Sonar IMO, so I'm inclined to update our Sonar config accordingly
https://docs.sonarqube.org/7.7/analysis/analysis-parameters/
sonar.cpd.exclusions
sonar.cpd.${language}.minimumtokens
sonar.cpd.${language}.minimumLines

Steps

• npm install
• npm custom script

Combo

• core validation build script
  • npm i
  • npm run build
  • publish test results
  • publish code coverage
• core validation test and lint
  • npm i
  • npm test
  • npm run lint
  • publish test results
  • publish code coverage

Should be self-explanatory

Create root/landing documentation to explain contents, links out to specific docs for various language templates, etc.

Add step template for running cargo license (https://github.com/onur/cargo-license) to generate license data for dependencies