Matt Mitchell
Matt Mitchell
DotNetPublishUsingPIpelines unintentionally meant "publishing or not". DotNetPublishUsingPipelines should never have been used to differentiate actually publishing vs. not. It was only used to differentiate two types of publishing, and it...
We need to migrate dotnetbuilds over to AzureFD due to the [Edgio CDN going away](https://learn.microsoft.com/en-us/azure/frontdoor/migrate-cdn-to-front-door). Unlike dotnetcli, we **can** change the hostname in the places it is referenced (dotnetbuilds.azureedge.net). dotnetbuilds...
Remove all uses of DotNetPublishUsingPipelines. It is the default, and false basically just disables publishing, which can just be done by not passing **-publish**. Remove switch in Arcade (implicitly true...
There are quite a few places that read and write asset manifests between Arcade, UB infrastructure, and Maestro/Darc functionality. We would ideally unify these on one. There is one already...
Currently publishing resides mostly in arcade, and runs as a service in the promotion pipelines. All .NET versions use this same problem (not bifurcated by release). This is by design....
Where necessary, move the data in the ReleaseConfig into the merged manifest.
Enable incremental binary SDL analysis in pipelines and the staging pipeline for caching performance gains: ``` extends: template: v1/1ES.Official.PipelineTemplate.yml@1ESPipelineTemplates parameters: featureFlags: incrementalSDLBinaryAnalysis: true ```
Where possible, avoid using PublishPipelineArtifact and PublishBuildArtifacts. Instead, use outputs:. These are much more efficient as incremental SDL and binary analysis can be enabled.
The build promotion pipeline has a combination of queue time variables and parameters. It is SO confusing. It should only use parameters.