google-code-backups / xinc

Automatically exported from code.google.com/p/xinc
0 stars 0 forks source link

PHPUnit tests, PHPDoc documentation, and Change Log don't show up #189

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. ${dir} points to the project root
2. PHPUnit puts test results into ${dir}/reports and html formatted results
in ${dir}/reports/tests, used the formatter in phing to create noframes output.
3. Using "<phpUnitTestResults file="${dir}/reports/testsuites.xml" />"
inside the <publishers> tag
4. Also put "<documentation file="${dir}/apidoc" alias="PHPUnit Results"
index="${dir}/results/tests/index.html" />"
5. PHPDoc puts its output into ${dir}/apidoc
6. Using "<documentation file="${dir}/apidoc" alias="PHPDoc API
Documentation" index="${dir}/apidoc/index.html" />" to include the
documentation.

What is the expected output? What do you see instead?
I don't see any documentation links, the PHPUnit summary below the
Artifacts box, or the Change Log box. I see those on http://xinc.eu, but
not on my server.

What version of the product are you using? On what operating system?
Using the version of Xinc installed by running "pear install
http://xinc.eu/api/deliverable/get/download/xinc/1209313148/Xinc.tgz" on
the command line.

Ubuntu Gutsy, PHP5 (5.2.3-1ubuntu6.4), Apache2.2 (2.2.4-3build1)

This is what shows up in the build log ( project name changed to protect
the guilty =D, and toned down a bit ):

<message priority="info" > PROJECTNAME: Processing publishers done></message>
<message priority="info" > PROJECTNAME: Registering test results:
/var/xinc/projects/PROJECTNAME/reports/testsuites.xml->/var/xinc/status/PROJECTN
AME/20090109/1231467501/testresults/testsuites.xml,
result: OK></message>
<message priority="info" > Publishing with OnSuccess Publisher:
Xinc_Plugin_Repos_Publisher_PHPUnitTestResults_Task></message>
<message priority="error" > PROJECTNAME: --  is not within project dir.
Security Problem.></message>
<message priority="error" > PROJECTNAME: Registering doc:
->/var/xinc/status/PROJECTNAME/20090109/1231467501/documentation/PHPUnit/
failed.></message>
<message priority="debug" > PROJECTNAME: Trying to register documentation:
/var/xinc/projects/PROJECTNAME/results/tests></message>
<message priority="info" > PROJECTNAME: Publishing with OnSuccess
Publisher: Xinc_Plugin_Repos_Publisher_Documentation_Task></message>
<message priority="error" > PROJECTNAME: --  is not within project dir.
Security Problem.></message>
<message priority="error" > PROJECTNAME: Registering doc:
->/var/xinc/status/PROJECTNAME/20090109/1231467501/documentation/PHPDoc/
failed.></message>
<message priority="debug" > PROJECTNAME: Trying to register documentation:
/var/xinc/projects/PROJECTNAME/apidoc></message>
<message priority="info" > PROJECTNAME: Publishing with OnSuccess
Publisher: Xinc_Plugin_Repos_Publisher_Documentation_Task></message>
<message priority="info" > PROJECTNAME: Registering deliverable:
/var/xinc/projects/PROJECTNAME/builds/build_BUILD.1.tar.gz->/var/xinc/status/PRO
JECTNAME/20090109/1231467501/deliverable/build_BUILD.1.tar.gz,
result: OK></message>
<message priority="debug" > PROJECTNAME: Trying to register deliverable:
/var/xinc/projects/PROJECTNAME/builds/build_BUILD.1.tar.gz></message>
<message priority="info" > PROJECTNAME: Publishing with OnSuccess
Publisher: Xinc_Plugin_Repos_Publisher_Deliverable_Task></message>

Please provide any additional information below.
Xinc is set to a one minute interval while I'm testing, and set to build
always. Once I have this sorted out, it'll be switched to a one hour
interval, and to only build if the SVN repo has changed. If the Change Log
doesn't show up till Xinc updates the local working copy itself, then it'd
be nice to have that in the documentation for Xinc. 

Does Xinc have to update the local working copy itself for the Modification
Summary to get updated as well? I'd much rather do an SVN export in phing,
so that the build tarball isn't full of .svn folders that aren't needed.

Original issue reported on code.google.com by sean.ha...@gmail.com on 9 Jan 2009 at 2:11

GoogleCodeExporter commented 8 years ago
I re-installed Xinc through pear, and now the PHPUnit tests show up on the build
status page. Still getting the same error about "-- is not within project dir"
though. It looks almost like the attributes from the documentation tag for the
index,alias,and file aren't getting passed to the php script that handles the
documentation. I'm going to do some more testing and see if I can figure out 
what's
going wrong.

Original comment by sean.ha...@gmail.com on 16 Jan 2009 at 6:18

GoogleCodeExporter commented 8 years ago
Okay, figured it out.

Turns out I had just put the wrong path in the file and index attributes for the
documentation tag. But I had to go into Xinc/Plugin/Repos/Documentation.php and 
add a
bunch of $build->info() lines to figure this out. Would it be possible to have 
the
Documentation give more meaningful errors when it fails like this?

Original comment by sean.ha...@gmail.com on 16 Jan 2009 at 6:41

GoogleCodeExporter commented 8 years ago
tk

Original comment by arjun.an...@gmail.com on 1 Jun 2009 at 7:34

GoogleCodeExporter commented 8 years ago

Original comment by opitz.al...@googlemail.com on 19 Aug 2011 at 1:40

GoogleCodeExporter commented 8 years ago

Original comment by opitz.al...@googlemail.com on 20 Aug 2011 at 10:31