You can disable that part, see
https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#source-code-blames-for-git-projects
<https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#source-code-blames-for-git-projects>
> Am 04.06.2020 um 08:31 schrieb Amedee Van Gasse <amedee.vanga...@gmail.com>:
>
> Warnings Next Generation Plugin provides a build step `recordIssues`.
>
> I found that it hangs for several minutes on
>
> /usr/bin/git rev-parse HEAD^{commit}
>
> Before I knew which Jenkins plugin was responsible, I asked on Stack Overflow
> 10 days ago, but of course didn't get (nor expect) a useful answer.
>
> https://stackoverflow.com/questions/61973411/jenkins-pipeline-during-recordissues-for-checkstyle-pmd-spotbugs-git-rev-pars
>
> <https://stackoverflow.com/questions/61973411/jenkins-pipeline-during-recordissues-for-checkstyle-pmd-spotbugs-git-rev-pars>
>
> This is the relevant part of the Jenkinsfile:
>
> stage('Static Code Analysis') {
> options {
> timeout(time: 1, unit: 'HOURS')
> }
> steps {
> withMaven(jdk: "${JDK_VERSION}", maven: 'M3', mavenLocalRepo:
> '.repository') {
> sh 'mvn --no-transfer-progress verify --activate-profiles qa
> -Dpmd.analysisCache=true'
> }
> recordIssues(tools: [
> checkStyle(),
> pmdParser(),
> spotBugs(useRankAsPriority: true)
> ])
> dependencyCheckPublisher pattern: 'target/dependency-check-report.xml'
> }
> }
> This is an excerpt from the Jenkins console log:
>
> 00:10:26.471 [CheckStyle] Successfully parsed file
> /home/ubuntu/jenkins/workspace/iText_7_Java_itextcore_develop/target/checkstyle-result.xml
> 00:10:26.471 [CheckStyle] -> found 0 issues (skipped 0 duplicates)
> 00:10:26.847 using credential bd100583-6d56-496a-89c0-67e640c2f80e
> 00:10:27.322 using credential bd100583-6d56-496a-89c0-67e640c2f80e
> 00:10:26.896 > /usr/bin/git rev-parse HEAD^{commit} # timeout=10
> 00:10:27.699 using credential bd100583-6d56-496a-89c0-67e640c2f80e
> 00:10:28.173 using credential bd100583-6d56-496a-89c0-67e640c2f80e
> 00:10:27.748 > /usr/bin/git rev-parse HEAD^{commit} # timeout=10
> 00:12:10.218 > /usr/bin/git rev-parse HEAD^{commit} # timeout=10
> 00:25:35.352 [CheckStyle] Post processing issues on 'jenkins-node-aws' with
> source code encoding 'UTF-8'
> 00:25:35.352 [CheckStyle] Creating SCM blamer to obtain author and commit
> information for affected files
> 00:25:35.352 [CheckStyle] -> Git blamer successfully created in working tree
> '/home/ubuntu/jenkins/workspace/iText_7_Java_itextcore_develop'
> 00:25:35.352 [CheckStyle] Creating SCM miner to obtain statistics for
> affected repository files
> 00:25:35.352 [CheckStyle] -> Git miner successfully created in working tree
> '/home/ubuntu/jenkins/workspace/iText_7_Java_itextcore_develop'
> 00:25:35.352 [CheckStyle] Resolving file names for all issues in source
> directory '/home/ubuntu/jenkins/workspace/iText_7_Java_itextcore_develop'
> 00:25:35.352 [CheckStyle] -> resolved paths in source directory (1238 found,
> 0 not found)
> 00:25:35.352 [CheckStyle] Resolving module names from module definitions
> (build.xml, pom.xml, or Manifest.mf files)
> 00:25:35.352 [CheckStyle] -> resolved module names for 85004 issues
> 00:25:35.352 [CheckStyle] Resolving package names (or namespaces) by parsing
> the affected files
> 00:25:35.352 [CheckStyle] -> resolved package names of 1238 affected files
> 00:25:35.352 [CheckStyle] No filter has been set, publishing all 85004 issues
> 00:25:35.352 [CheckStyle] Creating fingerprints for all affected code blocks
> to track issues over different builds
> 00:25:35.352 [CheckStyle] -> created fingerprints for 85004 issues (skipped
> 0 issues)
> 00:25:35.352 [CheckStyle] Invoking Git blamer to create author and commit
> information for 1238 affected files
> 00:25:35.352 [CheckStyle] GIT_COMMIT env = 'HEAD'
> 00:25:35.352 [CheckStyle] Git commit ID =
> '62d4a2abfda51f58acac8f4ce8e799dffcdbfb0a'
> 00:25:35.352 [CheckStyle] Git working tree =
> '/home/ubuntu/jenkins/workspace/iText_7_Java_itextcore_develop'
> 00:25:35.352 [CheckStyle] -> blamed authors of issues in 1238 files
> 00:25:35.352 [CheckStyle] Blaming of authors took 498 seconds
> 00:25:35.352 [CheckStyle] Analyzing the commit log of the Git repository
> '/home/ubuntu/jenkins/workspace/iText_7_Java_itextcore_develop'
> 00:25:35.352 [CheckStyle] Invoking Git miner to create statistics for all
> available files
> 00:25:35.352 [CheckStyle] Git working tree =
> '/home/ubuntu/jenkins/workspace/iText_7_Java_itextcore_develop'
> 00:25:35.352 [CheckStyle] -> created statistics for 1238 files
> 00:25:35.352 [CheckStyle] -> created report for 1238 files in 69 seconds
> 00:25:35.352 [CheckStyle] Copying affected files to Jenkins' build folder
> '/var/lib/jenkins/jobs/iText_7_Java/jobs/itextcore/branches/develop/builds/910/files-with-issues'
> 00:25:35.352 [CheckStyle] -> 1238 copied, 0 not in workspace, 0 not-found, 0
> with I/O error
> 00:28:49.752 [CheckStyle] Using reference build
> 'iText_7_Java/itextcore/develop #909' to compute new, fixed, and outstanding
> issues
> 00:28:49.752 [CheckStyle] Issues delta (vs. reference build): outstanding:
> 85002, new: 2, fixed: 2
> 00:28:49.752 [CheckStyle] No quality gates have been set - skipping
> 00:28:49.752 [CheckStyle] Health report is disabled - skipping
> 00:28:49.752 [CheckStyle] Created analysis result for 85004 issues (found 2
> new issues, fixed 2 issues)
> 00:28:49.752 [CheckStyle] Attaching ResultAction with ID 'checkstyle' to run
> 'iText_7_Java/itextcore/develop #910'.
> Notice the jump in time stamp from 00:10:27.748 to 00:12:10.218 to
> 00:25:35.352. I see a similar (although less extreme) jump in time stamps
> when Jenkins is doing the recordIssues for PMD and SpotBugs.
>
> This takes too long for just running git rev-parse and the delay is
> unacceptable. 13 minutes of doing absolutely nothing useful. No other jobs
> were running at the time. What is going on here and how to fix it?
>
> EDIT:
>
> The delay is NOT, and I repeat: NOT in the mvn command. It is in the
> recordIssues command.
>
> EDIT:
>
> It is not just with Checkstyle
> It is also with PMD and Spotbugs
> EDIT:
>
> recordIssues is a Jenkins pipeline build step that comes from Warnings Next
> Generation Plugin.
> https://www.jenkins.io/doc/pipeline/steps/warnings-ng/#recordissues-record-compiler-warnings-and-static-analysis-results
>
> <https://www.jenkins.io/doc/pipeline/steps/warnings-ng/#recordissues-record-compiler-warnings-and-static-analysis-results>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/aae1f3ea-ab17-4f79-9628-e1d0bdf7e170%40googlegroups.com
>
> <https://groups.google.com/d/msgid/jenkinsci-users/aae1f3ea-ab17-4f79-9628-e1d0bdf7e170%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/810BB759-9BBE-424B-9AFC-2949DBAE0B8A%40gmail.com.
