Jenkins Sonar Job aborted by anonymous. Weird job

2019-07-18 23:36发布

I keep facing very weird issue integrating Jenkins and Sonar. I have a maven project that I build and run SonarQube analysis via maven command line (with import of the Sonar server predefined variables). When I run the Jenkins job first time, it may be green. The next job is "aborted by anonymous" without any logs provided. The third job is getting broken build with 401 error, saying I am not authorized to Sonar.

If I re-enter and re-save THE SAME PASSWORD to the Jenkins Sonar configuration, I may get the green build for one time again.

Has anyone faced such kind of Jenkins Poltergeist before and what could be the issue?

EDIT: after every "first green build", Jenkins auto-restarts and resets credentials in most of my plugins (i.e. SonarQube, Gerrit-Sonar). This influences only username\password pairs, not SSH credentials.

EDIT #2: Maven version: 3.3.9

Jenkins version: 1.653

SonarQube Plugin Version: 2.4.4

0条回答
登录 后发表回答