what Jenkins are you speaking about? Is it your instance? And does it succeed after 4:30 hours?
A lot of reasons could do that:
1/ Your are using a clean Maven repository in each build so you're redownloading all the dependencies
2/ Something is broken at provisining machines at Jenkins
3/ You executor is swapping heavily
I suspect 1/ has the biggest probabilaty.
Btw, you can use Arquillian Drone to make Selenium usage much easier: