{"id":58080,"date":"2019-11-13T09:00:20","date_gmt":"2019-11-13T17:00:20","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/devops\/?p=58080"},"modified":"2019-11-12T12:54:01","modified_gmt":"2019-11-12T20:54:01","slug":"uploading-to-codecov-just-got-easier","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/uploading-to-codecov-just-got-easier\/","title":{"rendered":"Uploading to Codecov just got easier"},"content":{"rendered":"

How do you know your tests actually exercise your code? Perhaps you’re using a code coverage tool like coverage.py<\/a> or the tools built into Visual Studio<\/a>. Codecov<\/a> helps you track code coverage: how much of your code is covered, and are you getting more coverage over time? By integrating Codecov into your continuous integration (CI) pipeline, you’ll get great reports that help you improve your coverage. You can read more about Codecov on their features page<\/a>.<\/p>\n

Using Codecov<\/h2>\n

It’s really easy to get started. Codecov offers a results uploader<\/a> you can run without having to install any additional tools. The script figures out what language your project is written in, where the coverage results are, and how to get them to the service. Typically when you integrate outside services into your CI pipeline, you also need to manage one or more secrets. These secrets – think passwords and certificates – are required to securely talk to the outside service.<\/p>\n

Codecov has a clever feature in their Bash uploader: tokenless upload for public pipelines. By doing a little extra validation on their side, Codecov saves users the trouble of managing secrets. This only works for public projects on specific CI providers, and I’m happy to announce that now, Azure Pipelines<\/a> is one of them. (If you have private pipelines on Azure Pipelines or anyplace else, you can still use Codecov and will need to manage a token.)<\/p>\n

Connecting with Azure Pipelines<\/h2>\n

To give it a try for yourself, clone one of Codecov’s example repos<\/a>. I like Python<\/a>, so that’s where I started. It’s a toy Python project with two methods and one test. You’ll have to change two things about that example repo:<\/p>\n

    \n
  1. Replace .travis.yml with an Azure Pipelines YAML definition. <\/li>\n
  2. Instead of using the Python codecov<\/code> uploader, rely on the Bash uploader. <\/li>\n<\/ol>\n

    Here’s my example Azure Pipelines file:<\/p>\n

    trigger:\n- master\n\npool:\n  vmImage: 'ubuntu-latest'\nstrategy:\n  matrix:\n    Python35:\n      python.version: '3.5'\n    Python36:\n      python.version: '3.6'\n    Python37:\n      python.version: '3.7'\n\nsteps:\n- task: UsePythonVersion@0\n  inputs:\n    versionSpec: '$(python.version)'\n  displayName: 'Use Python $(python.version)'\n\n- script: |\n    python -m pip install --upgrade pip\n    pip install coverage\n  displayName: 'Install coverage'\n\n- script: |\n    coverage run tests.py\n  displayName: 'Run tests'\n\n- script: |\n    bash <(curl -s https:\/\/codecov.io\/bash)\n  displayName: 'Upload to codecov.io'\n<\/code><\/pre>\n
    Showing it off<\/h2>\n
    After I install the Codecov GitHub app and run this pipeline, Codecov handles the rest for me. Here’s an example of the graphs it generates:<\/p>\n
    \"Screen<\/a><\/p>\n
    I get ongoing coverage reports without having to add or manage secrets in my pipeline. Thanks to the folks over at Codecov for adding Azure Pipelines to their tokenless upload infrastructure.<\/p>\n","protected":false},"excerpt":{"rendered":"
    Codecov.io added tokenless uploading of coverage results for public Azure Pipelines.<\/p>\n","protected":false},"author":719,"featured_media":58085,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[224,226],"tags":[],"class_list":["post-58080","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure","category-ci"],"acf":[],"blog_post_summary":"
    Codecov.io added tokenless uploading of coverage results for public Azure Pipelines.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/58080","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/719"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=58080"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/58080\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/58085"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=58080"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=58080"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=58080"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}