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

Migrate to 1ES template migration for official builds and mark others accordingly #7253

Merged
merged 2 commits into from Mar 26, 2024

Conversation

arkalyanms
Copy link
Member

@arkalyanms arkalyanms commented Mar 20, 2024

Validation build is at https://dev.azure.com/dnceng/internal/_build/results?buildId=2410326&view=results. (SBOM publishing failure warning pending. Should not be a blocker though.)

@arkalyanms arkalyanms requested a review from a team as a code owner March 20, 2024 00:55
Copy link

codecov bot commented Mar 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.48%. Comparing base (29bdbf5) to head (e1f3661).
Report is 4 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff            @@
##             main    #7253    +/-   ##
========================================
  Coverage   96.48%   96.48%            
========================================
  Files        1439     1442     +3     
  Lines      344369   345212   +843     
  Branches    11324    11345    +21     
========================================
+ Hits       332259   333082   +823     
- Misses       9244     9256    +12     
- Partials     2866     2874     +8     

azure-pipelines-microbuild.yml Outdated Show resolved Hide resolved
azure-pipelines-perf.yml Outdated Show resolved Hide resolved
azure-pipelines-microbuild.yml Show resolved Hide resolved
Copy link
Member

@Cosifne Cosifne left a comment

Choose a reason for hiding this comment

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

A minor question about the parameter. Other looks good

outputs:
# Archive NuGet packages to DevOps.
- output: pipelineArtifact
path: $(Build.ArtifactStagingDirectory)/packages/$(BuildConfig)
Copy link
Contributor

@jjonescz jjonescz Mar 25, 2024

Choose a reason for hiding this comment

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

Previously the path was 'artifacts\packages\$(_BuildConfig)' now it's $(Build.ArtifactStagingDirectory)/packages/$(BuildConfig) which seems to resolve to D:\a\_work\1\a\packages\Release which looks different and probably is the reason why you're getting failures in the CI run ##[error]Path does not exist: D:\a\_work\1\a\packages\Release

Applies to the output below as well.

@jjonescz jjonescz merged commit 00071ec into main Mar 26, 2024
11 checks passed
@jjonescz jjonescz deleted the dev/arkalyan/1es-migrate branch March 26, 2024 11:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants