Skip to content
This repository was archived by the owner on Apr 20, 2023. It is now read-only.

[DO NOT MERGE] updated to coherence 26448 & templating build 298#7250

Closed
seancpeters wants to merge 1 commit intodotnet:release/2.0.0from
seancpeters:update_to_coherence_26448
Closed

[DO NOT MERGE] updated to coherence 26448 & templating build 298#7250
seancpeters wants to merge 1 commit intodotnet:release/2.0.0from
seancpeters:update_to_coherence_26448

Conversation

@seancpeters
Copy link
Copy Markdown

No description provided.

Copy link
Copy Markdown

@mikeharder mikeharder left a comment

Choose a reason for hiding this comment

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

@mlorbetske and I discussed waiting for 26452 since it was built with a newer CLI with an updated Roslyn version. Either 26452 or 26448 should be fine, but we might as well wait if we're hoping this is our final insertion.

@seancpeters
Copy link
Copy Markdown
Author

Mike, Bala, & I went back n forth on doing this one. We wanted to get a newer version out tonight, for CTI to test. Then we'll get the 26452 insertion done tomorrow

Copy link
Copy Markdown

@mikeharder mikeharder left a comment

Choose a reason for hiding this comment

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

OK, inserting 26448 is fine with me, then we can try to decide whether inserting 26452 is even worth it. I doubt the Roslyn change in the CLI has any impact on ASP.NET packages.

@seancpeters
Copy link
Copy Markdown
Author

Looks like we don't yet have no-timestamp versions of:

  • Microsoft.AspNetCore.All
  • Microsoft.VisualStudio.Web.CodeGeneration.Tools

@mikeharder
Copy link
Copy Markdown

Good catch. @JunTaoLuo, do you know the status of the non-timestamped versions of these packages?

@mikeharder
Copy link
Copy Markdown

@seancpeters: I do see non-timestamped versions of these packages in the output of CoherenceSigned. Where do you see they are missing?

@seancpeters
Copy link
Copy Markdown
Author

Mike H. & I talked about this offline, but for others following along: the errors with the package versions are in the failed builds, for example:
https://ci.dot.net/job/dotnet_cli/job/release_2.0.0/job/debug_windows_nt_x86_prtest/668/
https://ci.dot.net/job/dotnet_cli/job/release_2.0.0/job/debug_ubuntu16.10_x64_prtest/641/

@mikeharder
Copy link
Copy Markdown

I believe the issue is the non-timestamped packages have not been published to https://dotnet.myget.org/gallery/aspnetcore-ci-release, and the test is expecting this feed to contain them. The fix is to either publish the non-timestamped packages to this feed, or publish them to another feed (i.e. a verification feed) and update the test to include this feed.

@mlorbetske
Copy link
Copy Markdown

There's a verification feed that Pranav and Eilon have for uploading the no-timestamp packages to & the NuGet.config needs to be updated to point at it.

@mlorbetske
Copy link
Copy Markdown

From NuGet.config

<add key="aspnet" value="https://dotnet.myget.org/F/aspnetcore-release/api/v3/index.json" />
<!-- Replace the aspnet entry above with this one when we switch to no-timestamp packages -->
<!-- add key="aspnet" value="https://dotnet.myget.org/F/aspnet-2-0-0-rtm/api/v3/index.json" / -->
<add key="websdkfeed" value="https://dotnet.myget.org/F/dotnet-web/api/v3/index.json" />

@JunTaoLuo
Copy link
Copy Markdown

Unfortunately we don't build the no-timestamp version of the .All metapackage until Conherence-Signed so it is only available on the aspnetcore-release and aspnetcore-dev (i.e. signed) feeds. Not sure about the .Tools packages though. I'm assuming those should be on the aspnetcore-ci-dev and aspnetcore-ci-release feeds so it might be a problem somewhere in our build.

@seancpeters
Copy link
Copy Markdown
Author

@dotnet-bot test this please

@livarcocc livarcocc changed the title updated to coherence 26448 & templating build 298 [DO NOT MERGE] updated to coherence 26448 & templating build 298 Jul 25, 2017
@mikeharder
Copy link
Copy Markdown

@seancpeters, @mlorbetske: Can you please update this PR to use ASP.NET build 26452? This is our target final build.

@nguerrera
Copy link
Copy Markdown
Contributor

Superseded by #7262

@nguerrera nguerrera closed this Jul 25, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants