当前位置: 首页 > 面试题库 >

詹金斯·乔布失败

向修谨
2023-03-14
问题内容

我已经安装了运行Jenkins的uberSVN服务器,以使用PHP-WebWare控制SVN存储库。

我一直在遇到问题,并一直在寻找解决方案。现在,我希望这是最后一个,但是我找不到任何答案:

Publishing Clover coverage report...
Publishing Clover HTML report...
Publishing Clover XML report...
Publishing Clover coverage results...
[htmlpublisher] Archiving HTML reports...
[htmlpublisher] Archiving at BUILD level /opt/ubersvn/jenkins/workspace/JenkinsTest/build/api to /opt/ubersvn/jenkins/jobs/JenkinsTest/builds/2013-03-12_12-56-15/htmlreports/API_Documentation
ERROR: Directory '/opt/ubersvn/jenkins/workspace/JenkinsTest/build/api' exists but failed copying to '/opt/ubersvn/jenkins/jobs/JenkinsTest/builds/2013-03-12_12-56-15/htmlreports/API_Documentation'.
ERROR: This is especially strange since your build otherwise succeeded.
Build step 'Publish HTML reports' changed build result to FAILURE

这里是Jenkins.log

12.03.2013 12:56:17 hudson.model.Run run
INFO: JenkinsTest #37 main build action completed: SUCCESS

谁能告诉我这里的问题是什么?

编辑:这里-为了更好的分析-完整的日志

Building in workspace /opt/ubersvn/jenkins/workspace/JenkinsTest
Cleaning up /opt/ubersvn/jenkins/workspace/JenkinsTest/.
Deleting /opt/ubersvn/jenkins/workspace/JenkinsTest/./cache.properties
Deleting /opt/ubersvn/jenkins/workspace/JenkinsTest/./build/API_Documentation
Deleting /opt/ubersvn/jenkins/workspace/JenkinsTest/./build/api
Deleting /opt/ubersvn/jenkins/workspace/JenkinsTest/./build/code-browser
Deleting /opt/ubersvn/jenkins/workspace/JenkinsTest/./build/coverage
Deleting /opt/ubersvn/jenkins/workspace/JenkinsTest/./build/logs
Deleting /opt/ubersvn/jenkins/workspace/JenkinsTest/./build/pdepend
Deleting /opt/ubersvn/jenkins/workspace/JenkinsTest/./build/phpdox
Updating http://svn.xyz.de:80/JenkinsTest/trunk
At revision 25
no change for http://svn.xyz.de:80/JenkinsTest/trunk since the previous build
[JenkinsTest] $ ant
Unable to locate tools.jar. Expected to find it in /opt/ubersvn/jre1.6.0_24-64/lib/tools.jar
Buildfile: /opt/ubersvn/jenkins/workspace/JenkinsTest/build.xml

clean:

prepare:
    [mkdir] Created dir: /opt/ubersvn/jenkins/workspace/JenkinsTest/build/api
    [mkdir] Created dir: /opt/ubersvn/jenkins/workspace/JenkinsTest/build/API_Documentation
    [mkdir] Created dir: /opt/ubersvn/jenkins/workspace/JenkinsTest/build/code-browser
    [mkdir] Created dir: /opt/ubersvn/jenkins/workspace/JenkinsTest/build/coverage
    [mkdir] Created dir: /opt/ubersvn/jenkins/workspace/JenkinsTest/build/logs
    [mkdir] Created dir: /opt/ubersvn/jenkins/workspace/JenkinsTest/build/pdepend
    [mkdir] Created dir: /opt/ubersvn/jenkins/workspace/JenkinsTest/build/phpdox

lint:
    [apply] No syntax errors detected in /opt/ubersvn/jenkins/workspace/JenkinsTest/src/index.php
    [apply] No syntax errors detected in /opt/ubersvn/jenkins/workspace/JenkinsTest/tests/bootstrap.php

phploc:
     [exec] phploc 1.7.4 by Sebastian Bergmann.
     [exec] 
     [exec] Lines of Code (LOC):                                  2
     [exec]   Cyclomatic Complexity / Lines of Code:           0.00
     [exec] Comment Lines of Code (CLOC):                         0
     [exec] Non-Comment Lines of Code (NCLOC):                    2
     [exec] 
     [exec] Namespaces:                                           0
     [exec] Interfaces:                                           0
     [exec] Traits:                                               0
     [exec] Classes:                                              0
     [exec]   Abstract:                                           0 (0.00%)
     [exec]   Concrete:                                           0 (0.00%)
     [exec]   Average Class Length (NCLOC):                       0
     [exec] Methods:                                              0
     [exec]   Scope:
     [exec]     Non-Static:                                       0 (0.00%)
     [exec]     Static:                                           0 (0.00%)
     [exec]   Visibility:
     [exec]     Public:                                           0 (0.00%)
     [exec]     Non-Public:                                       0 (0.00%)
     [exec]   Average Method Length (NCLOC):                      0
     [exec]   Cyclomatic Complexity / Number of Methods:       0.00
     [exec] 
     [exec] Anonymous Functions:                                  0
     [exec] Functions:                                            0
     [exec] 
     [exec] Constants:                                            0
     [exec]   Global constants:                                   0
     [exec]   Class constants:                                    0

pdepend:
     [exec] PHP_Depend 1.1.0 by Manuel Pichler
     [exec] 
     [exec] Parsing source files:
     [exec] .                                                                1
     [exec] 
     [exec] Executing Coupling-Analyzer:
     [exec] .     0
     [exec] 
     [exec] Executing CyclomaticComplexity-Analyzer:
     [exec] .     0
     [exec] 
     [exec] Executing Dependency-Analyzer:
     [exec] .     0
     [exec] 
     [exec] Executing Inheritance-Analyzer:
     [exec] .     0
     [exec] 
     [exec] Executing NodeCount-Analyzer:
     [exec] .     0
     [exec] 
     [exec] Executing NodeLoc-Analyzer:
     [exec] .     0
     [exec] 
     [exec] Generating pdepend log files, this may take a moment.
     [exec] 
     [exec] Time: 00:00; Memory: 7.75Mb

phpmd-ci:

phpcs-ci:

phpcpd:
     [exec] phpcpd 1.4.0 by Sebastian Bergmann.
     [exec] 
     [exec] 0.00% duplicated lines out of 2 total lines of code.
     [exec] 
     [exec] Time: 0 seconds, Memory: 2.25Mb

phpdox:
     [exec] phpdox 0.4.0 - Copyright (C) 2010 - 2012 by Arne Blankerts
     [exec] 
     [exec] 
     [exec] An error occured while trying to load the configuration file:
     [exec]     None of the candidate files found
     [exec] 
     [exec] Using --skel might get you started.
     [exec] 
     [exec] Result: 3

phpunit:
     [exec] hiPHPUnit 3.7.18 by Sebastian Bergmann.
     [exec] 
     [exec] Configuration read from /opt/ubersvn/jenkins/workspace/JenkinsTest/phpunit.xml.dist
     [exec] 
     [exec] 
     [exec] 
     [exec] Time: 0 seconds, Memory: 3.75Mb
     [exec] 
     [exec] No tests executed!
     [exec] 
     [exec] Generating code coverage report in Clover XML format ... done
     [exec] 
     [exec] Generating code coverage report in HTML format ... done

phpcb:

build:

BUILD SUCCESSFUL
Total time: 1 second
[CHECKSTYLE] Collecting checkstyle analysis files...
[CHECKSTYLE] Finding all files that match the pattern build/logs/checkstyle.xml
[CHECKSTYLE] Parsing 1 files in /opt/ubersvn/jenkins/workspace/JenkinsTest
[CHECKSTYLE] Successfully parsed file /opt/ubersvn/jenkins/workspace/JenkinsTest/build/logs/checkstyle.xml of module  with 0 warnings.
[PMD] Collecting PMD analysis files...
[PMD] Finding all files that match the pattern build/logs/pmd.xml
[PMD] Parsing 1 files in /opt/ubersvn/jenkins/workspace/JenkinsTest
[PMD] Successfully parsed file /opt/ubersvn/jenkins/workspace/JenkinsTest/build/logs/pmd.xml of module  with 0 warnings.
[DRY] Collecting duplicate code analysis files...
[DRY] Finding all files that match the pattern build/logs/pmd-cpd.xml
[DRY] Parsing 1 files in /opt/ubersvn/jenkins/workspace/JenkinsTest
[DRY] Successfully parsed file /opt/ubersvn/jenkins/workspace/JenkinsTest/build/logs/pmd-cpd.xml of module  with 0 warnings.
Recording plot data
Publishing Clover coverage report...
Publishing Clover HTML report...
Publishing Clover XML report...
Publishing Clover coverage results...
[htmlpublisher] Archiving HTML reports...
[htmlpublisher] Archiving at BUILD level /opt/ubersvn/jenkins/workspace/JenkinsTest/build/API_Documentation to /opt/ubersvn/jenkins/jobs/JenkinsTest/builds/2013-03-12_14-11-41/htmlreports/API_Documentation
ERROR: Directory '/opt/ubersvn/jenkins/workspace/JenkinsTest/build/API_Documentation' exists but failed copying to '/opt/ubersvn/jenkins/jobs/JenkinsTest/builds/2013-03-12_14-11-41/htmlreports/API_Documentation'.
ERROR: This is especially strange since your build otherwise succeeded.
Build step 'Publish HTML reports' changed build result to FAILURE
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing PHPUnit-3.x (default)
[xUnit] [INFO] - [PHPUnit-3.x (default)] - 1 test report file(s) were found with the pattern 'build/logs/junit.xml' relative to '/opt/ubersvn/jenkins/workspace/JenkinsTest' for the testing framework 'PHPUnit-3.x (default)'.
[xUnit] [WARNING] - All test reports are empty.
[xUnit] [INFO] - Check 'Failed Tests' threshold.
[xUnit] [INFO] - Check 'Skipped Tests' threshold.
[xUnit] [INFO] - Setting the build status to FAILURE
[xUnit] [INFO] - Stopping recording.
[JDepend] JDepend plugin is ready
[JDepend] Found 0 classes in 0 packages
Finished: FAILURE

不知道对您有没有帮助

做到了!!!

只需在项目根目录中定义phpdox.xml

<phpdox xmlns="http://phpdox.de/config">
    <project name="name-of-project" source="src" workdir="build/phpdox">
        <collector publiconly="false">
            <include mask="*.php" />
            <exclude mask="*Autoload.php" />
        </collector>

        <generator output="build">
            <build engine="html" enabled="true" output="api"/>
        </generator>
    </project>
</phpdox>

很抱歉浪费您的时间:/ jenkins-php.org必须进行更新,以使新的Jenkins用户更容易^^


问题答案:

就算有人没有读过我的编辑:

做到了!!!

只需在项目根目录中定义phpdox.xml

<phpdox xmlns="http://phpdox.de/config">
    <project name="name-of-project" source="src" workdir="build/phpdox">
        <collector publiconly="false">
            <include mask="*.php" />
            <exclude mask="*Autoload.php" />
        </collector>

        <generator output="build">
            <build engine="html" enabled="true" output="api"/>
        </generator>
    </project>
</phpdox>

抱歉浪费您的时间:/ jenkins



 类似资料:
  • 问题内容: 我有一个.Jar文件,它将在运行时将数据加载到数据库中。我已经计划通过詹金斯来担任这项工作。当我在詹金斯执行作业时,它将成功运行.JAR。但是,请说作业中是否存在空指针异常,并且该异常未成功完成。即便如此,詹金斯仍然说工作已经“通过”。如果作业执行过程中出现问题,如何使作业失败? 问题答案: @Corey的解决方案很好。而且,如果您不想编写JUnit测试并在Jenkins中提供支持,则

  • 有没有可能让詹金斯使用真正的浏览器而不是无头浏览器?我正在运行一些用TestNG编写的测试(使用Selenium webdriver)。当我运行testng时。在Eclipse中,浏览器启动并运行测试。但当我使用Jenkins并用maven运行测试时,它不会启动任何浏览器。

  • 问题内容: 我已经使用Jenkins为我的node js应用程序创建了CI管道。我的管道包括诸如构建,单元测试,集成测试,代码分析等工作。我知道默认情况下,即使一个测试用例失败,构建也会失败。 问题答案: 您的单元测试脚本将需要处理数学和逻辑,以确定失败的测试百分比足以使整个工作失败。然后,您的单元测试脚本可以返回通过(零)或失败(其他任何结果),詹金斯将相应地标记构建。

  • 本地maven运行良好。然而,詹金斯未能发射它。我注意到下面的反斜杠,但不确定它来自哪里: $java-cp C:\windows\system32\config\systemprofile.jenkins\plugins\maven-plugin\WEB-INF\lib\maven31-agent-1.5.jar;C:\tes\apache-maven-3.2.5-bin\apache-mave

  • 问题内容: 如何轻松地将Jenkins与qUnit集成?我将使用真正的浏览器(如firefox和chrome)运行测试。我的服务器在RedHat 6.1 Linux上运行。我想我都需要插件/库,但我仍然不知道如何使其工作。我第一次与Jenkins合作(在服务器端)。 //编辑: 如果有人也可以共享想法如何构建覆盖率报告,那将是很棒的。 提前致谢 :)。 问题答案: 说詹金斯和QUnit只是难题的一

  • 我想做一些非常简单的事情,在一个文件夹中,我有一个jar文件和一个包含脚本的名为脚本的文件夹。但我可以让詹金斯拉链来做这件事。 zip目录:“awsdeploy”,排除:“”,glob:“”,“scripts/”,zipFile:“SQSToElasticProcessor.zip” 必须显式命名“zip”的参数。@ 第 31 行,第 16 列。