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

[pull] main from microsoft:main #172

Merged
merged 1 commit into from
Oct 3, 2023
Merged

Commits on Oct 2, 2023

  1. build: add a OneBranch Official release pipeline (#16081)

    This pipeline does everything the existing release pipeline does, except
    it does it using the OneBranch official templates.
    
    Most of our existing build infrastructure has been reused, with the
    following changes:
    
    - We are no longer using `job-submit-windows-vpack`, as OneBranch does
    this for us.
    - `job-merge-msix-into-bundle` now supports afterBuildSteps, which we
    use to stage the msixbundle into the right place for the vpack
    - `job-build-project` supports deleting all non-signed files (which the
    OneBranch post-build validation requires)
    - `job-build-project` now deletes `console.dll`, which is unused in any
    of our builds, because XFGCheck blows up on it for some reason on x86
    - `job-publish-symbols` now supports two different types of PAT
    ingestion
    - I have pulled out the NuGet filename variables into a shared variables
    template
    
    I have also introduced a TSA config (which files bugs on us for binary
    analysis failures as well as using the word 'sucks' and stuff.)
    
    I have also baselined a number of control flow guard/binary analysis
    failures.
    DHowett authored Oct 2, 2023
    Configuration menu
    Copy the full SHA
    6489f6b View commit details
    Browse the repository at this point in the history