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

Remove various single-scenario YAML parameters in our build scripts and shift implementation responsibility to those scenarios #100115

Merged
merged 7 commits into from
Apr 12, 2024

Conversation

jkoritzinsky
Copy link
Member

Uses Arcade defaults (defaults to false/empty string) to remove richCodeNavigation property.

Inline CodeQL injection to the CodeQL pipeline

Use Arcade's Source-Build jobs now that we aren't using any features that require the steps support.

CodeQL run at https://dev.azure.com/dnceng/internal/_build/results?buildId=2411429&view=results
Official Build at https://dev.azure.com/dnceng/internal/_build/results?buildId=2411430

…nd shift implementation responsibility to those scenarios.

Uses Arcade defaults to remove richCodeNavigation property.

Inline CodeQL injection to the CodeQL pipeline

Use Arcade's Source-Build jobs now that we aren't using any features that require the steps support.
Copy link
Contributor

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Copy link
Member

@hoyosjs hoyosjs left a comment

Choose a reason for hiding this comment

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

Looks reasonable if official build passes

parameters:
platforms:
- name: CentOS8
targetRid: centos.8-x64
Copy link
Member

Choose a reason for hiding this comment

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

Isn't CentOS EOL soon?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, but I wanted to preserve existing behavior in this PR to limit possible issues.

@@ -145,10 +145,6 @@
<RelativeBlobPath>$(InstallersRelativePath)workloads/%(Filename)%(Extension)</RelativeBlobPath>
<PublishFlatContainer>true</PublishFlatContainer>
</ItemsToPush>

<!-- Source build intermediated packages will be pushed and signed by the sourcebuild leg. -->
Copy link
Member

Choose a reason for hiding this comment

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

How come this changed

Copy link
Member Author

Choose a reason for hiding this comment

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

Now that we aren't pushing a copy of the source-build artifacts into the IntermediateArtifacts artifact, we can remove this code that filters it out.

# as a stash of a shallow cloned repo is not currently supported.
${{ if ne(parameters.isSourceBuild, true) }}:
fetchDepth: $(checkoutFetchDepth)
fetchDepth: $(checkoutFetchDepth)
Copy link
Member

Choose a reason for hiding this comment

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

Who sets this for SB?

Copy link
Member Author

Choose a reason for hiding this comment

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

SourceBuild has never had this set (due to the comment above).

@jkoritzinsky jkoritzinsky merged commit c2848c5 into dotnet:main Apr 12, 2024
149 of 152 checks passed
@jkoritzinsky jkoritzinsky deleted the remove-yaml-single-use branch April 12, 2024 18:10
matouskozak pushed a commit to matouskozak/runtime that referenced this pull request Apr 30, 2024
…nd shift implementation responsibility to those scenarios (dotnet#100115)
@github-actions github-actions bot locked and limited conversation to collaborators May 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants