Isn't that what PIP is for? Either improve or leave.

Since it sounds like he's doing it on purpose (malicious compliance), if it's happening several times already and you've already explained to him what the correct process is.

Don't get me wrong, I'm all for giving people second and third chances, have a talk with them and see what the problem is, maybe they have issues with their health or their personal life, but people who engage in malicious compliance because they can't be bothered to follow a simple process need to be shown the door pronto as that attitude negatively affect the whole team.

If you can afford to and you have a team dynamic where "everyone makes mistakes" you can give them more responsibility -- like other people being stuck until they actually fix the build. But that can backfire if they're very junior or the culture is very negative around making mistakes.

Otherwise asking them questions can help. Come from the place that you must be missing something and ask them why you can't get XYZ to work as expected. Make them figure out what the problem is. Really get in the mindset that you're missing something though, or it can come off as patronizing.

If it's anything like companies I've worked at, you stick them in an unimportant fiefdom and give them raises, promos, and refreshers for decades.

Can you ask for proof?

Tests passing, screenshots/gif of build fix in action, etc