The user needs to open the console output for the build and will try to see if any file changes that were missed during building the project.
If there aren't any problems on it then a much better approach would be clean and update his local workspace to copy the problem on their local machine and will try to solve it.
To make sure Jenkins build isn't broken in the slightest degree we need to make sure that we tend to perform a successful clean install on the local machine with all unit tests.
Then make sure that all code changes are checked in without any issues.
Then synchronize with a repository to make sure that all needed config and changes and any variations are checked into the repository.