Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[main] Add CodeQL3000 tasks #8160

Merged
merged 2 commits into from
Nov 23, 2022
Merged

Conversation

dougbu
Copy link
Member

@dougbu dougbu commented Nov 17, 2022

  • cherry-pick from [3.x] Add CodeQL3000 tasks #8159 branch, with slight adjustments
  • enable CodeQL in this branch
    • use explicit tasks to enable manual builds of any branch
  • add a new top-level parameter to enable CodeQL3000 in manual builds
  • tag CodeQL3000 builds that do actual CodeQL3000 work
  • add a tsaoptions.json file
    • initial area path value is certainly wrong
    • other values may be incorrect too
Microsoft Reviewers: Open in CodeFlow

@dougbu
Copy link
Member Author

dougbu commented Nov 17, 2022

Just kicked off build #20221116.4 for actual validation w/ CodeQL3000 enabled.

/cc @ReubenBond @benjaminpetit

@dougbu
Copy link
Member Author

dougbu commented Nov 17, 2022

That test build ran the tasks but didn't do much because the CodeQL analysis was considered up to date. Merging this PR will

  • enable manual builds to test CodeQL
  • limit the number of regular builds affected by (slowed by) CodeQL to internal scheduled and, optionally, manual builds
  • report bugs found in the TSA database

The middle bullet doesn't apply to #8159 because 3.x is not the repo's default branch. Only the default branch gets the tasks auto-injected (unless disabled, as I did in this PR).

{
"areaPath": "DevDiv\\ASP.NET Core",
"codebaseName": "Orleans",
"instanceUrl": "https://devdiv.visualstudio.com/",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we are still building on our own devops instance, should we change this value?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know because the documentation of this file format is sorely lacking. I suspect this is the location where areaPath lives and where TSA bugs will be filed. Suggest we probably want to keep @danmoseley's bug in the same instance. @dcwhittaker do you know more❔

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this can be resolved since this instance is definitely where the area path lives.

- `cherry-pick` from dotnet#8159 branch, with slight adjustments
- enable CodeQL in this branch
  - use explicit tasks to enable manual builds of any branch
- add a new top-level parameter to enable CodeQL3000 in manual builds
- tag CodeQL3000 builds that do actual CodeQL3000 work
- add a tsaoptions.json file
  - initial area path value is certainly wrong
  - other values may be incorrect too
@dougbu dougbu force-pushed the dougbu/CodeQL3000/main branch from 315aa2b to 1783f73 Compare November 22, 2022 19:34
@dougbu
Copy link
Member Author

dougbu commented Nov 22, 2022

Rebased on main and switched to the right area path. This PR should be ready to go unless @ReubenBond's #8159 (comment) comment needs additional changes both here and there.

@dougbu
Copy link
Member Author

dougbu commented Nov 22, 2022

I can't rerun workflows in this repo to clear up the unsuccessful check

@ReubenBond
Copy link
Member

That unsuccessful check seems to be unrelated. I'm going to investigate, but we can ignore it for this PR

@ReubenBond ReubenBond merged commit f320f49 into dotnet:main Nov 23, 2022
@dougbu dougbu deleted the dougbu/CodeQL3000/main branch November 30, 2022 19:19
@github-actions github-actions bot locked and limited conversation to collaborators Dec 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants