[jira] Issue Comment Edited: (IVY-582) Non-standard temp directory causes failure uploading checksum files

["Anson Mayers (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IVY-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516812 ] 

Anson Mayers edited comment on IVY-582 at 8/2/07 2:14 PM:
----------------------------------------------------------

Please make sure when attempting to reproduce that you run JDK 1.5.0_09's jre and use Ivy 2.0.0 alpha build 1 on Windows.  I am not sure if there is a sensitivity to the slash direction, so please make sure to use Windows-style slashes.  I saw no stack traces in the log when running -v or -d, though I did notice one interesting thing:

[ivy:resolve]   resolve done (47ms resolve - 0ms download)
 [property] Loading E:\ca\teamcity-harvest-plugin\trunk\lib\..\build\temp\delivery.properties
 [property] Unable to find property file: E:\ca\teamcity-harvest-plugin\trunk\lib\..\build\temp\delivery.properties

This delivery.properties file is also not being found in the tmpdir when the system property java.io.tmpdir contains '..'.


 was:
Please make sure when attempting to reproduce that you run JDK 1.5.0_09's jre and use Ivy 2.0.0 alpha build 1 on Windows.  I am not sure if there is a sensitivity to the slash direction, so please make sure to use Windows-style slashes.  I saw no stack traces in the log when running -v or -d, though I did notice one interesting thing:

[ivy:resolve]   resolve done (47ms resolve - 0ms download)
 [property] Loading E:\ca\teamcity-harvest-plugin\trunk\lib\..\build\temp\delive
ry.properties
 [property] Unable to find property file: E:\ca\teamcity-harvest-plugin\trunk\li
b\..\build\temp\delivery.properties

This delivery.properties file is also not being found in the tmpdir when the system property java.io.tmpdir contains '..'.

> Non-standard temp directory causes failure uploading checksum files
> -------------------------------------------------------------------
>
>                 Key: IVY-582
>                 URL: https://issues.apache.org/jira/browse/IVY-582
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.0.0-alpha-1
>         Environment: Running Ivy inside Ant, spawned by Atlassian TeamCity (a build tool you might call 'CruiseControl on steroids'), on Windows XP.  2x Duo Core Intel processors.
>            Reporter: Anson Mayers
>            Priority: Minor
>
> Here's the critical piece of the output:
> [ivy:publish] :: publishing :: [ ca | harvest-intellij-plugin ]
> I00060040: New connection with Broker cscr612 established.
> I0009002d: Information: build has successfully logged into Harvest broker cscr612 .
> I00020100: File D:\ca\idea-harvest-plugin\trunk-nightly\build\artifacts\bin-zips\harvest-intellij-plugin-1.0.8.zip checked into \ivy-repository\ca\harvest-intellij-plugin\bin-zips\harvest-intellij-plugin-1.0.8.zip;0 .
> I00060079: Check in summary: Total: 1 ; Success: 1 ; Failed: 0 ; Not Processed: 0 .
> I00060040: New connection with Broker cscr612 established.
> I0009002d: Information: build has successfully logged into Harvest broker cscr612 .
> E03020028: The File Agent error for item D:\BuildAgent\bin\..\temp\teamcity.tmp\harvest-intellij-plugin-1.0.8.zip.sha1 : No such file or directory .
> E03060019: Process Execute failed. Process Name: Check In Items . I00060079: Check in summary: Total: 1 ; Success: 0 ; Failed: 1 ; Not Processed: 0 .
> As you can see, I have written a custom publisher, which works fine if not invoked from within the TeamCity environment.  In that case, the *.sha1 file is read from C:\Documents and Settings\dev\Local Settings\temp\harvest-intellij-plugin-1.0.8.zip.sha1, and the publish succeeds.  TeamCity, it seems, has its own ideas about what the temp directory should be, and the resulting path is not resolved by the publisher.
> It is possible that the presence of ".." in the temp path is problematic.  The directory itself (D:\BuildAgent\temp\teamcity.tmp) does exist, and has some subfolders suggesting that other processes have written to it (i.e. hsperfdata_dev, etc.).  I have searched the hard drive for the *.sha1 file, to see if it was written somewhere else, but cannot find it anywhere.
> This environment is difficult to debug.  However, based on a suggestion in a comment on a different bug, I did add the following to the build, immediately before the call to publish:
>   <echo level="error">${java.io.tmpdir}</echo>
> The resulting output was as expected:
>     [echo] D:\BuildAgent\bin\..\temp\teamcity.tmp
> The complete command line of the JVM that experiences the problem is (line feeds added for easier reading, note java.io.tmpdir is specified):
> D:\ca\jdks\jdk1.5.0_09\bin\java.exe
>  "-Dteamcity.buildConfName=IntelliJ Harvest Plugin Trunk Nightly"
>  -DDotNetFramework1.1_Path=C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
>  -Dbuild.working.dir=D:\ca\idea-harvest-plugin\trunk-nightly
>  -Dagent.name=rwc-cm132
>  -Dbuild.number=1.0.12
>  -DDotNetFramework1.1=
>  -Dbuild.number.format=1.0.{0}
>  -Duser.language=en
>  -Duser.country=US
>  -Dos.version=5.2
>  -Duser.timezone=America/Los_Angeles
>  -Dfile.encoding=Cp1252
>  -DDotNetFramework2.0_x86=
>  "-Dteamcity.projectName=IHP TN"
>  -Dfile.separator=\
>  -Dagent.work.dir=F:\ca\work
>  -DDotNetFramework2.0_x86_Path=C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
>  -DDotNetFramework2.0_Path=C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
>  -Dos.arch=x86
>  -DDotNetFramework1.1_x86_Path=C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
>  -DDotNetFramework1.1_x86=
>  -DDotNetFramework2.0=
>  -Djava.io.tmpdir=D:\BuildAgent\bin\..\temp\teamcity.tmp
>  -Dbuild.vcs.number.1=2007-07-25-18-08-52-544
>  -Dgroup=platform-smoke,platform-nightly,cade-smoke,cade-nightly,teamcity-harvest-plugin-smoke,idea-harvest-plugin-nightly,idea-harvest-plugin-smoke,teamcity-harvest-plugin-nightly
>  -Duser.name=SYSTEM
>  "-Dos.name=Windows 2003"
>  -Dant.task.extensions=jetbrains.buildServer.agent.ant.CompilerAntExtension,jetbrains.buildServer.agent.ant.EchoAntExtension,jetbrains.buildServer.coverage.AntCoverageAdapter,jetbrains.buildServer.testng.TestNGTaskExtension,
>  -Didea.build.agent.port=9090
>  -Dteamcity.auth.userId=TeamCityBuildId=2333
>  -Dteamcity.buildType.id=bt27
>  -Duser.variant=
>  -Dagent.classpath=D:/BuildAgent/lib/buildServerXmlRpcWrapper.jar;D:/BuildAgent/lib/xstream-1.2.1.jar;D:/BuildAgent/lib/utils.jar;D:/BuildAgent/plugins/coveragePlugin/lib/buildServerCoverageAgent.jar;D:/BuildAgent/lib/buildServerServerLogging.jar;
> D:/BuildAgent/plugins/coveragePlugin/lib/emma.jar;D:/BuildAgent/lib/xmlrpc-2.0.1.jar;D:/BuildAgent/lib/commons-codec-1.3.jar;D:/BuildAgent/lib/xpp3_min-1.1.3.4.M.jar;D:/BuildAgent/lib/nanocontainer-1.0-RC-1.jar;
> D:/BuildAgent/plugins/testNGPlugin/lib/testNGAntExtension.jar;D:/BuildAgent/plugins/antPlugin/lib/buildServerAntServerLogging.jar;D:/BuildAgent/lib/buildServerCommonRuntime.jar;D:/BuildAgent/lib/buildServerMessages.jar
>  -Dsuccessful.build.number=1.0.1
>  "-Duser.home=C:\Documents and Settings\Default User"
>  -Didea.build.server.build.id=2333
>  -Dant.home=D:\ca\cade\trunk-nightly\tools
>  -Dpath.separator=;
>  -classpath D:\ca\cade\trunk-nightly\toaols\lib\ant-launcher.jar
>  org.apache.tools.ant.launch.Launcher
>  -Dcade.home=D:\ca\cade\trunk-nightly
>  -lib D:/BuildAgent/lib/buildServerRuntimeUtil.jar;D:/BuildAgent/plugins/antPlugin/lib/buildServerAntRuntime.jar
>  -listener jetbrains.buildServer.agent.ant.AgentBuildListener
>  -buildfile D:\ca\idea-harvest-plugin\trunk-nightly\build.xml
>  autobuild-nightly-build 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.