Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
/ corefx Public archive

Add separate symbol publish (index/archive) build leg #18350

Merged
merged 1 commit into from
Apr 25, 2017

Conversation

dagood
Copy link
Member

@dagood dagood commented Apr 13, 2017

See #16939.

This switches indexing to use VSTS Symbol. It handles hosting, so the builds don't need to copy to a file share. For release branch builds, archiving performance (still using the file share) is improved by dotnet/buildtools#1421.

The time this leg's steps take for a daily/indexed build is now:

  • 6.4 minutes Extracting
  • 1.5 minutes Publishing (indexing)
  • Total: 7.9 minutes

I removed the symbol publishing steps from the Windows build legs because they're redundant. Removing the publish target path from the index+publish step means it will only index sources for the symbols and won't copy them anywhere. (Edit: on a test build I see that this step is only finding 2 PDBs, and it isn't able to find sources for them. Getting symbol indexing working properly is tracked by https://github.com/dotnet/core-eng/issues/499.)

Remove unused variable PB_SymbolsBuildIdRoot
@danmoseley
Copy link
Member

@dagood still in progress?

@dagood
Copy link
Member Author

dagood commented Apr 25, 2017

@danmosemsft Yes, waiting for review.

Copy link
Member

@weshaggard weshaggard left a comment

Choose a reason for hiding this comment

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

I don't really like all the inline PS scripts but I can live with them.

Overall LGTM.

@dagood
Copy link
Member Author

dagood commented Apr 25, 2017

I don't really like all the inline PS scripts

Agreed. There is a new VSTS feature for conditions on steps that would let us stop doing that (without extra buildtools work), but our toolchain doesn't support it yet.

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.

5 participants