The Evolving Infrastructure of .NET Core

Re:The Evolving Infrastructure of .NET Core by idlemind on Sunday July 07, 2019 @05:09AM (#20374242)

It’s nice to see the .NET Core team hitting on the same solution as we are heading for internally for our multi-repo builds - the “dependency flow” with Maestro sounds very similar to what we intend to do with propagating latest NuGet package versions to consumers via PRs, then auto-merging those PRs if all checks pass (and the repo owner has opted into this, of course).

Will the .NET Core team open source this tooling I wonder?

[ Parent | on HN ]

Re:The Evolving Infrastructure of .NET Core by moksly on Sunday July 07, 2019 @05:18AM (#20374261)

I think they would very much like you to buy into Azure. We’re a C# shop, have been for decades, and .Net Core really shines when you hook it up to the Azure devops package. Which is perfectly fine for us, we’re in bed with Microsoft anyway and with office365 licenses for 4500 employees, Windows enterprise for 5000 and a farm of local windows servers that’s what we would have likely done anyway.

[ Parent | on HN ]

Re:The Evolving Infrastructure of .NET Core by idlemind on Sunday July 07, 2019 @06:10AM (#20374404)

Yes I got that impression. Azure DevOps wouldn’t be the right solution for us unfortunately.

[ Parent | on HN ]

Re:The Evolving Infrastructure of .NET Core by noahl on Sunday July 07, 2019 @12:34PM (#20375926)

Out of curiosity, what makes it not the right solution? (I work on the Azure DevOps team.)

[ Parent | on HN ]

Re:The Evolving Infrastructure of .NET Core by idlemind on Monday July 08, 2019 @03:19AM (#20380582)

Our build system very much needs to be on-premises for the foreseeable future.

[ Parent | on HN ]

Re:The Evolving Infrastructure of .NET Core by mmitche on Tuesday July 09, 2019 @05:27PM (#20396805)

It already is actually, though general purpose use was not intended.

https://github.com/dotnet/arcade-services

[ Parent | on HN ]