Improve runtime-codeql pipeline to run more compliance tooling

Open
#115,526 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
ci-cd, security

Research direction

Read the runtime-codeql pipeline and its compliance-tooling steps first, focusing on where binskim is invoked. Done means the compliance tooling covers the intended runtime outputs and the pipeline runs successfully.

Written by the indexing model from the issue text.

Description

area-Infrastructure

We recently moved our compliance tooling runs from the runtime official build to the runtime-codeql pipeline.

As part of this work, we discovered that tools like binskim aren't running on much of our outputs. We should adjust that pipeline as needed to ensure that we're getting full coverage of our compliance tooling in the runtime repo.

cc: @ericstj @jeffschwMSFT

Dominant language
C#
Stars
18.3k
Forks
5.6k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.