-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Enable Policheck #33841
Enable Policheck #33841
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as long as the official build is green.
I highly recommend linking to it from this PR to make it easy to look at the results. |
@Anipik, should this be merged? |
I think this should be addressed first: #33841 (comment) It is really helpful for the comment to link to the variable group. |
i moved it to here. https://github.com/dotnet/runtime/pull/33841/files#diff-2601d29fabf2d8fa57d58b3eb4ff8d17R28 The variable group is still not recognised , can you suggest the appropriate place ?
This post build stage is still not getting passed on the actual build https://dev.azure.com/dnceng/internal/_build/results?buildId=579800 i am working with the arcade folks to get it fixed. |
Right, but this won't work because the
You need to add it to this section which is where we declare the yml variables: Once you put it there it should work. Since it will be in a different template, add the comment back referencing the variable group. Also, since |
@Anipik we want to port this into preview3 as just discussed in Tactics. |
linking the issues |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doing this in official builds seems like the wrong approach. We should be catching this at PR time.
@@ -29,6 +29,12 @@ jobs: | |||
pool: | |||
name: Hosted VS2017 | |||
steps: | |||
- task: UseDotNet@2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be done in arcade instead, this is part of eng/common/*
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes they will be taking in the change as well, if the solution solves the problems
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing the reject for now as this is apparently the intended path forward. Going to be following up separately on removing this from official builds as this will seemingly reduce official build reliability. Want us to persue other alternatives here, rolling builds, separate pipelines in the internal project or ideally PR validation.
@Anipik what's the status on this? |
I have scheduled an official build to test the change as well