Why despite declarations in multiple repos of providing daily core-sdk builds they are more or less biweekly? about installer HOT 4 CLOSED

I am not sure what you mean here.

We build based on PRs merged. This means that for every PR merged, we kick off builds that will produce nightly builds. I can see in our build's history, the last build we did was on 9/13, which succeeded and results in the build liked in our readme page.

So, after this PR was merged, we didn't merge other PRs and therefore there were no more builds.

That's our promise. We will not kick off daily builds without any diff in them because they are effectively the same as previous ones.

If I misunderstood your point I am sorry, please clarify and we will try to address that as well.

Lastly, we have a bunch of infra-structure in flight and changes happening, which means some builds may get delayed.

I see that you also mentioned corefx builds. While we guarantee builds for every PR on core-sdk, there is no guarantee that that core-sdk build will contain the last corefx bits immediately. if that's something that you do, you can acquire those bits independently of the SDK through core-setup or separate packages.

from installer.

This is not an answer to my question and ask.

So, after this PR was merged, we didn't merge other PRs and therefore there were no more builds.

The changes are flowing into core-sdk every day in the form of core-setup updates and they are not merged everyday what is the reason for lack of builds.

That's our promise. We will not kick off daily builds without any diff in them because they are effectively the same as previous ones.

The diffs are present in core-sdk dependencies. core-sdk is rather not very active and due to that there is no reason to block dependency flow from other repos.

cc @terrajobst @jkotas @danmosemsft

from installer.

Pace of development in coreclr and corefx repos is very high and there are multiple new features and fixes added daily

Yes, pace of development is very high in .NET Core overall and there are also intentional breaking changes or unintentional bugs introduced daily. The system we have in place where every repo states its known good dependencies is there to allow us to deal with these breaks and bugs, without putting the system to halt.

We have tried a system where we built latest version of everything together. It did not work. Getting one build through was a heroic effort that took a days or even weeks.

We have a feature in our backlog to auto-merge these "Update dependencies" PRs if they are green. It will help with less active repos not merging these frequently enough.

If your changes are in CoreCLR/CoreFX, you can try to pick core-setup builds and unzip it over your SDK. The CoreCLR/CoreFX changes propagate to core-setup (ie. .NET Core Runtime) faster since it is several layers below core-sdk (ie .NET Core SDK).

from installer.

We have a feature in our backlog to auto-merge these "Update dependencies" PRs if they are green. It will help with less active repos not merging these frequently enough.

Thanks for explanation. Implementing this feature would be very very helpful

from installer.