The word drop in damn near every expression of software development means one of two things:
1. To dispose of
2. A drag target
What does MS call drop? a place for successful staging of build results, aka artifacts. WTF! Artifacts?!?
A common trait of software engineers is to have one solution with 2 or more executable front ends. This would entail two artifacts. MS makes it as clear as mud in midnight of a cloud covered sky with no moon as to how to do this.
I am close to tossing the whole CICD process again, and just manually push everything, because the MS process, using YAML no less, is written for insane people who have no clue how to talk to people who’s primary code is to service users.
People complain that Angular has a harsh learning curve, but at least their samples are relevant, complete, and useful. Everything that the MS DevOps build pipes are not.
At least give us a standardized dictionary that explains these terms in plain English, and not circular reference back to other confusing and obscure term usages, so that we are not using the best guess.
I don’t like the fix to this, but they are:
- Option 1, Drop everything that you have in Core 2.x and update it to the latest Core framework. Don’t fall behind, because if you do, you are bound to get screwed by MS.
- Option 2, make your own build servers and ignore all of the build server offerings that MS supplies.
- Option 3, Manhandle your YAML and expect to have to make changes to it every quarter, even if your code has no library or framework changes.
I realized that I hadn’t updated this. MS did fix the issue. Apparently they pissed of the community, and rolled back their change. Three of our company’s projects just started working “Miraculously”.