Jenkins Pipeline进程显然从未在.问题

r7knjye2  于 2024-01-07  发布在  Jenkins
关注(0)|答案(3)|浏览(275)

我被困在我的jenkins管道与sonarqube集成我读过其他职位和解决方案是更新持久的插件;然而我的插件是在最新版本v 493.v195aefbb0ff2
控制台输出:

  1. Injecting SonarQube environment variables using the configuration: sq1
  2. [Pipeline] {
  3. [Pipeline] sh
  4. process apparently never started in /var/lib/jenkins/workspace/DevOps Demo@tmp/durable-48ce628f
  5. (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
  6. [Pipeline] }
  7. WARN: Unable to locate 'report-task.txt' in the workspace. Did the SonarScanner succeed?
  8. [Pipeline] // withSonarQubeEnv
  9. [Pipeline] }
  10. [Pipeline] // stage
  11. [Pipeline] }
  12. [Pipeline] // withEnv
  13. [Pipeline] }
  14. [Pipeline] // withEnv
  15. [Pipeline] }
  16. [Pipeline] // node
  17. [Pipeline] End of Pipeline
  18. ERROR: script returned exit code -2
  19. Finished: FAILURE

字符串
我的Jenkinsfile如下

  1. pipeline {
  2. agent any
  3. environment {
  4. PATH = "/opt/maven"
  5. BUILD_ID = 'BUILD_NUMBER'
  6. }
  7. stages {
  8. stage('Get Code') {
  9. steps {
  10. echo 'Import code GitLab'
  11. updateGitlabCommitStatus name: 'build', state: 'pending'
  12. git branch: 'main', credentialsId: 'd6d909b7-d918-4ed3-b65f-426e3200a598', url: 'https://10.10.2.44/root/devops1.git'
  13. echo 'build step goes here'
  14. updateGitlabCommitStatus name: 'build', state: 'success'
  15. }
  16. }
  17. stage('SonarQube analysis') {
  18. steps {
  19. withSonarQubeEnv(credentialsId: 'jenkins-sq', installationName: 'sq1') {
  20. sh 'mvn sonar:sonar'
  21. }
  22. }
  23. }
  24. }
  25. }

qkf9rpyu

qkf9rpyu1#

路径错误,必须包含docker jenkins的“/bin”。

  1. environment {
  2. PATH = "/opt/maven:/bin"
  3. }

字符串

v64noz0r

v64noz0r2#

更正路径,如下所示:

  1. environment {
  2. PATH = "$PATH:/opt/maven:/bin:/usr/bin:usr/local/bin"
  3. }

字符串
我宁愿不覆盖整个PATH变量,而只是在其中添加更多的路径,并检查警告是否也会消失。

0mkxixxg

0mkxixxg3#

我也遇到了这个问题。首先,我升级了Jenkins持久插件,在我的情况下,这个解决方案并没有解决这个问题。经过深入调查,我发现PATH变量是问题所在。尝试在Jenkins环境中正确设置PATH变量。确保sh二进制文件从/bin位置可以在PATH上找到。您可以运行“which sh”来查看sh二进制文件的确切位置。

  1. environment {
  2. PATH = "/bin:/usr/bin:usr/local/bin"
  3. }

字符串

相关问题