Bugs item #2506115, was opened at 2009-01-14 04:50
Message generated for change (Comment added) made by drieseng
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=2506115&group_id=31650
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Tasks
Group: 0.86
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: steven maglio (smaglio81)
>Assigned to: Gert Driesen (drieseng)
Summary: copy task creates directory without permissions
Initial Comment:
The copy task has created a directory without any access privileges; not even
system admins could access/delete/modify the directory. This has happened twice
in the last year.
The similarities between the two occurrences:
* Both builds use the same build script.
* The build scipts delete and deploy to a remote/network location.
* The build script first deletes the directory. I also don't understand why
this delete task also deletes the directory.
<delete if="${directory::exists(deploy.version.dir)}" failonerror="false"
verbose="${verbose}">
<fileset basedir="${deploy.dir}">
<include name="**" />
</fileset>
</delete>
* The build copy's files to a directory that doesn't exist. But it seems that
copy tasks creates the target directory if it doesn't exist.
* The build script worked for weeks without a problem.
* Once the server image was restored, the build script again worked without
error.
* The build script is being executed as a task from CruiseControl.Net.
The differences between the occurrences are:
* Different versions of NAnt. The first one was with 0.85 and the second was
with 0.86.
* The remote/network locations where on two different servers.
Has anyone seen this happen before? Or have any suggestions on what to try in
order to prevent this from happening in the future?
TIA
----------------------------------------------------------------------
>Comment By: Gert Driesen (drieseng)
Date: 2009-01-19 20:48
Message:
Please reopen this bug report if the problem surfaces again.
----------------------------------------------------------------------
Comment By: steven maglio (smaglio81)
Date: 2009-01-18 11:25
Message:
I feel like a crazy man. I just reran the script and it runs without error,
even when the directory is already in existence.
Thank you both, oakinger and drieseng. Especially thank you to the lead
developer of NAnt!
oakinger -
I double checked, then deleted and recreated the permissions. I gave the
account "Full Control" permissions on the folder. If this problem comes up
again this will be the first place I check.
drieseng -
I attached the successful log just to alleviate all fears. But, if this
problem ever comes back, I will make sure to attached a log file with
"-verbose" to the initial bug request.
I appreciate all your help. Thank you All!
----------------------------------------------------------------------
Comment By: Gert Driesen (drieseng)
Date: 2009-01-18 10:03
Message:
Steven,
Please run NAnt in verbose mode (NAnt.exe -verbose ...), and attach the
output of a failed build.
Thanks!
----------------------------------------------------------------------
Comment By: Erich Eichinger (oakinger)
Date: 2009-01-18 08:09
Message:
Just ran the script w/o a problem. I recommend you check the folder
permissions (including propagation settings) of your target folder on
SANCTUM. Especially check for "CREATOR OWNER" permissions.
hth,
Erich
----------------------------------------------------------------------
Comment By: steven maglio (smaglio81)
Date: 2009-01-18 06:12
Message:
File Added: CopyToSanctum.bat
----------------------------------------------------------------------
Comment By: steven maglio (smaglio81)
Date: 2009-01-18 06:12
Message:
Our systems team requested that the deployment scripts be switched over to
use MSBuild until the NAnt problem could be looked into by more
knowledgeable NAnt developers. The developers at the meeting thought this
was silly because the issue happened so infrequently and in a manner that
was not reproducible. However, grudgingly, the scripts were rewritten into
MSBuild**.
But, tonight I needed to write a quick script to deploy files from
multiple build directories to a network drive (attached below). The script
will delete all files in a network drive's directory. Then it will copy the
new files into the network drive's directory.
When the location of the directory has not been created (aka,
-D:version=X.X.X.X is a way to specify a new directory location) the script
works perfectly. But, if the directory existed before the script is run,
then the permissions issue happens.
I guess this makes the error reproducible on our systems. If anyone reads
this bug report and can use the script (or a modified version) to test out
this error I would appreciate it.
**
Soapbox: My feelings on MSBuild so far are not optimistic.
Improvements/The Good: They gave every task the ability to produce output,
which can be useful. Loses/The Bad: 1) They use the Output feature
everywhere, at the detriment to code simplicity. 2) They have no direct
equivalent to <for> loops and <if> statements. And, 3) the manipulation of
filesets is really annoying.
File Added: CopyToSanctum.build
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=2506115&group_id=31650
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
