[
https://issues.jboss.org/browse/JBIDE-9266?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-9266:
-----------------------------------
I guess I could instead of creating the symlink on remote, create it on local and rsync it
to remote, since I'm now getting problems w/ host keys trying to sftp from local to
itself. :(
Note that using rsync -a is equivalent to --links, which is what I've been using to
preserve permissions and ownership:
-a, --archive archive mode; equals -rlptgoD (no -H,-A,-X)
-l, --links copy symlinks as symlinks
Replace/Extend latestBuild.html with a latest symbolic link
-----------------------------------------------------------
Key: JBIDE-9266
URL:
https://issues.jboss.org/browse/JBIDE-9266
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Fix For: 3.3.0.M3
I see we have more and more latestBuild.html present all over and I'm suggestion we
replace those with "latest" symbolic links instead.
Here is how to automate that on
downloads.jboss.org at least:
echo -e "rm latest\nln 2011-06-27_10-25-32-H2980 latest" | sftp
tools@filemgmt.jboss.org:/downloads_htdocs/tools/builds/nightly/trunk
The actual paths should of course be replaced with proper variable replacements.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira