"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
Azure DevOps (formerly Visual Studio Team Services, or VSTS, and before that Visual Studio Online, or VSO (not to be confused with the new Visual Studio Online which just offers Visual Studio, online)).
People may also be familiar with the on-premises version: Team Foundation Server, or TFS, which was re-branded as Azure DevOps Server.
I went for "other", but how could this be missed?
Maybe it's on the list, but under yet another name?
Found Jenkins a drag for C# development.
Everything required a plug-in, nothing came out of the box, and for some reason half of the plug-ins didn't support their new (at the time) pipelines as code model
That was about four years ago though, so maybe it's better now.