Intranoggin

Blither, Blather, Web Content Management.
Blog » Broken Pipeline EFCore Migrations

Broken Pipeline EFCore Migrations

Sometime between 11/06/2019 and 11/08/2019, our build pipeline was broken. 
brokenpipeline1.png
Digging into it a bit, I see this.
brokenpipeline2.png
and expanding that, I see this.
brokenpipeline3.png

Hmm. that's odd. 
It says Welcome to .NET Core 3.0, which was released recently.
It also says a possible reason is "You intended to execute a .NET Core program, but dotnet-ef does not exist."

so It seems to point to an issue with the change in tooling.

My first troubleshooting step is to just check to see if the tooling is working at all by seeing if i can generate the unicorn.
I add in a custom .NET Core action, as simple as i can: just execute the ef custom command: 
brokenpipeline4.png
But it failed with the same message
brokenpipeline5.png
So, I added another action in that installed the tooling, just like you would locally.
brokenpipeline6.png

And then, when I ran it, not only did the test ef core action pass and print out the unicorn, the rest of the build passed as well. Boom.
brokenpipeline7.png

Hopefully it's a temporary workaround. I don't think we should need to install the tooling for EF Core migrations to work, but at 22 seconds, it's not a deal breaker.


 
Posted: 11/8/2019 6:19:20 PM by Ryan Miller | with 0 comments