Thanks @Siarhei Hrabko Closing this ticket - thank you!

Changing tag name to v11.0.3 solved the problem

From John Malconian on Slack:

I've looked at this. It's a difficult problem to diagnose because I am able to build the module manually in the same environment that Jenkins is building the module. I have encountered problems like this before (builds locally, but doesn't build in Jenkins). My advice at this point is to get an extra set of eyes on the code and maven config to ensure there are no conflicting classpaths or anything like that. Maybe try releasing 11.0.3 and see if we get lucky. I'll try to think of other alternatives if that doesn't turn up anything.