[DO NOT MERGE] updated to coherence 26448 & templating build 298#7250
[DO NOT MERGE] updated to coherence 26448 & templating build 298#7250seancpeters wants to merge 1 commit intodotnet:release/2.0.0from
Conversation
mikeharder
left a comment
There was a problem hiding this comment.
@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.
|
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 |
mikeharder
left a comment
There was a problem hiding this comment.
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.
|
Looks like we don't yet have no-timestamp versions of:
|
|
Good catch. @JunTaoLuo, do you know the status of the non-timestamped versions of these packages? |
|
@seancpeters: I do see non-timestamped versions of these packages in the output of CoherenceSigned. Where do you see they are missing? |
|
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: |
|
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. |
|
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. |
|
From NuGet.config |
|
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. |
|
@dotnet-bot test this please |
|
@seancpeters, @mlorbetske: Can you please update this PR to use ASP.NET build |
|
Superseded by #7262 |
No description provided.