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

Builds are often breaking due to missing roslyn packages #4691

Closed
Sridhar-MS opened this issue Dec 25, 2015 · 11 comments
Closed

Builds are often breaking due to missing roslyn packages #4691

Sridhar-MS opened this issue Dec 25, 2015 · 11 comments
Assignees
Labels
Milestone

Comments

@Sridhar-MS
Copy link
Contributor

Currently all the builds are breaking due to missing Roslyn package -
Microsoft.CodeAnalysis.CSharp� 1.2.0-beta-20151215-01

The required version is not available in the myget feed @ https://www.myget.org/feed/roslyn-nightly/package/nuget/Microsoft.CodeAnalysis.CSharp

Failing builds
http://dotnet-ci.cloudapp.net/job/dotnet_cli/job/debug_osx/54/console
http://dotnet-ci.cloudapp.net/job/dotnet_cli/job/debug_ubuntu/61/console

cc: @jaredpar @agocke @piotrpMSFT

@TheRealPiotrP
Copy link
Contributor

Sounds gross, but maybe we should just take a * dependency until we get stable Roslyn pkgs...

@Sridhar-MS
Copy link
Contributor Author

@agocke Can you confirm that the roslyn version 1.2.0-beta1-20160108-01 used in the CLI is

  • pinned in myget?
  • PDBs indexed?
  • git tags added to the source code?

@agocke
Copy link
Member

agocke commented Jan 14, 2016

@Sridhar-MS That build has been uploaded to NuGet: https://www.nuget.org/packages/Microsoft.Net.Compilers.netcore/1.2.0-beta1-20160108-01

As for the rest, @brettfo I know some of the indexing services were down last, how are we doing on that? And do we still need to create a tag for the latest toolset?

@agocke
Copy link
Member

agocke commented Jan 14, 2016

I've tagged the release myself here: https://github.com/dotnet/roslyn/releases/tag/version-1.2.0-beta1-20160108-01

@Sridhar-MS
Copy link
Contributor Author

@brettfo Any idea about the PDBs indexing?

@brettfo
Copy link
Member

brettfo commented Jan 15, 2016

I'm not sure on the PDB indexing, but I do know that source archiving is still down and I suspect those two systems are related.

@tannergooding
Copy link
Member

@brettfo, PDB indexing for bits that end up on NuGet (publicly released) is a manual process and is not currently down. Whoever uploaded the netcore package to nuget should have ensured the proper process was kicked off for the public archiving of pdb bits.

@agocke
Copy link
Member

agocke commented Jan 15, 2016

@tannergooding Do we have documentation on this?

@brettfo
Copy link
Member

brettfo commented Jan 15, 2016

@agocke: Yes, we have some internal notes on this, I'll send you a pointer shortly.

Thanks to @tannergooding who reminded me where these instructions live. I've started the PDB archiving process and will report back here as soon as it's complete.

@brettfo
Copy link
Member

brettfo commented Jan 16, 2016

The PDB archiving build is now complete for the 1.2.0-beta1-20160108-01 build.

@Sridhar-MS
Copy link
Contributor Author

We moved all our required nuget packages into https://dotnet.myget.org/F/cli-deps/api/v3/index.json feed. So this issue is fixed.

wli3 referenced this issue in wli3/cli Jul 14, 2017
@msftgits msftgits transferred this issue from dotnet/cli Jan 31, 2020
@msftgits msftgits added this to the 1.0.0-rc2 milestone Jan 31, 2020
rainersigwald pushed a commit to rainersigwald/sdk that referenced this issue Jul 20, 2020
* Update dependencies from https://github.com/dotnet/sdk build 20200715.20

Microsoft.NET.Sdk
 From Version 3.1.400-preview.20360.11 -> To Version 3.1.400-preview.20365.20

* remove darc int feeds

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Jason Zhai <AzureTest@vwuzhai002.redmond.corp.microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants