Skip to content

Daily Builds link is not up to date in README #32055

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

Closed
eerhardt opened this issue Feb 10, 2020 · 9 comments · Fixed by #43392
Closed

Daily Builds link is not up to date in README #32055

eerhardt opened this issue Feb 10, 2020 · 9 comments · Fixed by #43392

Comments

@eerhardt
Copy link
Member

https://github.com/dotnet/runtime/tree/95cff585613585e06a316e850830ef6e401858af#daily-builds

The whole "Master" column is out of date. The "latest" daily build is the last one from core-setup. I'm going to delete that whole table until we can get a way to keep this table up to date. (Note that the other columns don't apply to this repo, so there is no sense putting them here. The servicing branches are in core-setup.)

Leaving this issue open to track some new way of getting a latest "Daily Build" link on our REAME.

/cc @dagood

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added area-Infrastructure-installer untriaged New issue has not been triaged by the area owner labels Feb 10, 2020
eerhardt added a commit to eerhardt/runtime that referenced this issue Feb 10, 2020
This section has been out of date since the repo consolidation. The Master column is from November - the last build from core-setup. The other columns don't make sense for this repo, since we don't service those releases from dotnet/runtime.

We can bring this table back when we get a way to keep the links up to date. See dotnet#32055 for tracking that.
stephentoub pushed a commit that referenced this issue Feb 10, 2020
This section has been out of date since the repo consolidation. The Master column is from November - the last build from core-setup. The other columns don't make sense for this repo, since we don't service those releases from dotnet/runtime.

We can bring this table back when we get a way to keep the links up to date. See #32055 for tracking that.
@dagood
Copy link
Member

dagood commented Feb 10, 2020

Currently the table is out of date since we didn't port the "latest" channel infra to the consolidated repo. I don't know a way to get info about the latest builds with public information, other than watching downstream repos for updates. (With Msft credentials, you can use Darc/BAR.)

Options:

@dotnet/runtime-infrastructure @mmitche


(Note that the other columns don't apply to this repo, so there is no sense putting them here. The servicing branches are in core-setup.)

dotnet/runtime is the place to file issues and track whatever's going on with core-setup servicing, so I think it makes some sense to have them here. We also got rid of master in core-setup, and the archive default branch simply points you here. There are no signposts to try looking at the servicing branches--if there were, maybe it would make sense to maintain the tables there. We produce the same set of artifacts here as we did in core-setup so it's not IMO significant that it's a different repo now.

(The POR has also been to use master and delete the tables from the release branches, but that's not an argument in itself. #3302)

/cc @NikolaMilosavljevic

@Symbai
Copy link

Symbai commented Feb 17, 2020

Is there a way for developers to at least manually get the daily builds somewhere else?

@stephentoub
Copy link
Member

@Symbai
Copy link

Symbai commented Feb 17, 2020

That's SDK bundle but I was referring to runtime only installers

@dagood
Copy link
Member

dagood commented Feb 18, 2020

A way to get it at the moment is look in this file for MicrosoftNETCoreAppRefPackageVersion:
https://github.com/dotnet/core-sdk/blob/master/eng/Versions.props#L72

E.g. 5.0.0-preview.1.20117.2

Assemble the URL of the artifact you're interested in using that version number:

https://dotnetcli.blob.core.windows.net/dotnet/Runtime/{version}/{name including version}

Example:
https://dotnetcli.blob.core.windows.net/dotnet/Runtime/5.0.0-preview.1.20117.2/dotnet-runtime-5.0.0-preview.1.20117.2-win-x64.exe

To get a build that hasn't merged into Core-SDK yet, you can look to see if there's an active auto-upgrade PR and grab the version from that: https://github.com/dotnet/core-sdk/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3Aapp%2Fdotnet-maestro+base%3Amaster

(Unfortunately not any way to look up build versions directly without Microsoft auth. dotnet/arcade-services#2566.)

@Symbai
Copy link

Symbai commented Feb 18, 2020

@dagood It is a bit complicated but unfortunately I need runtime only of the preview, so thank you for helping me out ❤

@dagood
Copy link
Member

dagood commented Mar 10, 2020

This should be unblocked soon per dotnet/arcade#4948.

#33230 contains this arcade update: dotnet/arcade@421b20f...d9a664e, which contains the commit from that PR. So, we're currently blocked on that auto-update.

Once this link suggested in the arcade PR works, I think we can move on this issue:
https://aka.ms/dotnet/net5/dev/Runtime/dotnet-apphost-pack-osx-x64.pkg

@dagood
Copy link
Member

dagood commented Mar 12, 2020

From an official build, looks like this is almost there and we got some links that work, but we hit this Arcade bug causing publish failure: dotnet/arcade#5044

  The following aka.ms links for blobs will be created:
    aka.ms/dotnet/net5/dev/Runtime/dotnet-apphost-pack-osx-x64.pkg -> https://dotnetcli.blob.core.windows.net/dotnet/Runtime/5.0.0-preview.3.20161.13/dotnet-apphost-pack-5.0.0-preview.3.20161.13-osx-x64.pkg
    aka.ms/dotnet/net5/dev/Runtime/dotnet-host-internal-osx-x64.pkg -> https://dotnetcli.blob.core.windows.net/dotnet/Runtime/5.0.0-preview.3.20161.13/dotnet-host-internal-5.0.0-preview.3.20161.13-osx-x64.pkg
    aka.ms/dotnet/net5/dev/Runtime/dotnet-hostfxr-internal-osx-x64.pkg -> https://dotnetcli.blob.core.windows.net/dotnet/Runtime/5.0.0-preview.3.20161.13/dotnet-hostfxr-internal-5.0.0-preview.3.20161.13-osx-x64.pkg
    aka.ms/dotnet/net5/dev/Runtime/dotnet-runtime-osx-x64.pkg -> https://dotnetcli.blob.core.windows.net/dotnet/Runtime/5.0.0-preview.3.20161.13/dotnet-runtime-5.0.0-preview.3.20161.13-osx-x64.pkg
    aka.ms/dotnet/net5/dev/Runtime/dotnet-runtime-internal-osx-x64.pkg -> https://dotnetcli.blob.core.windows.net/dotnet/Runtime/5.0.0-preview.3.20161.13/dotnet-runtime-internal-5.0.0-preview.3.20161.13-osx-x64.pkg
    aka.ms/dotnet/net5/dev/Runtime/dotnet-targeting-pack-osx-x64.pkg -> https://dotnetcli.blob.core.windows.net/dotnet/Runtime/5.0.0-preview.3.20161.13/dotnet-targeting-pack-5.0.0-preview.3.20161.13-osx-x64.pkg
D:\a\1\s\.packages\microsoft.dotnet.arcade.sdk\5.0.0-beta.20160.4\tools\SdkTasks\PublishArtifactsInManifest.proj(79,5): error : The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
...

@dagood
Copy link
Member

dagood commented Oct 14, 2020

@hoyosjs submitted a draft PR working on this: #43392. Thanks! 👍

@ghost ghost locked as resolved and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants