Rui Chen Not really deprecated, we just know it's terrible, and have known for a long time. For example, you'll see references to http://javaadventure.blogspot.de/2013/11/jenkins-maven-job-type-considered-evil.html written by a Maven committer on the Jenkins team occasionally. (Baptiste Mathus Or did I miss something?) For that reason, use is generally discouraged, but given how plugin dependencies work, it's just there on most instances. And since it's both convenient and does things no other plugin does, people continue using it. I don't think the Pipeline Maven Plugin is quite there yet.
thomas cornez config.xml might help, but not certain. Ideally you'll start Jenkins with an empty JENKINS_HOME. Do whatever is needed to make this issue appear, and take notes. If it's as easy as installing the plugins you have installed and dumping the job config.xml there so Jenkins loads it, that would be pretty straightforward. Then, do it again until you get streamlined steps to reproduce from scratch. Like Stack Overflow asking for minimal code samples, we're asking for minimal steps to reproduce. Less work and less errorprone that way.