[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9266) Replace/Extend latestBuild.html with a latest symbolic link

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-9266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616539#comment-12616539 ] 

Nick Boldt commented on JBIDE-9266:
-----------------------------------

Awesome. adding support for sftp-borne symlinking has caused a problem w/ publishing JBDS because that pushes over rsync to a LOCAL path, which sftp doesn't like.

Working on a hackaround now that says if DESTINATION path (/path/to/put/files) doesn't include user at server: prefix, use "hudson@`hostname -f`:/path/to/put/files" instead.



> 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 at 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