[ https://issues.jboss.org/browse/JBIDE-9266?page=com.atlassian.jira.plugin... ] Nick Boldt resolved JBIDE-9266. ------------------------------- Resolution: Rejected why would you ever need to use the /builds/ URL in Eclipse? That's why we have the /updates/ URLs. Latest Builds (browse in browser): http://download.jboss.org/jbosstools/builds/nightly/* Latest Updates (browse in Eclipse): http://download.jboss.org/jbosstools/updates/nightly/* -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9266?page=com.atlassian.jira.plugin... ] Nick Boldt edited comment on JBIDE-9266 at 7/15/11 11:53 AM: ------------------------------------------------------------- Currently, we do this. Fairly straightforward. Works on all mirrors (download.jboss, www.qa, and the Brno server): {code} echo "<meta http-equiv=\"refresh\" content=\"0;url=${BUILD_ID}-H${BUILD_NUMBER}/\">" > /tmp/latestBuild.html if [[ ${PUBLISHPATHSUFFIX} ]]; then date; rsync -arzq --delete ${STAGINGDIR}/* $DESTINATION/builds/nightly/${PUBLISHPATHSUFFIX}/${BUILD_ID}-H${BUILD_NUMBER}/ date; rsync -arzq --delete /tmp/latestBuild.html $DESTINATION/builds/nightly/${PUBLISHPATHSUFFIX}/ else date; rsync -arzq --delete /tmp/latestBuild.html $DESTINATION/builds/nightly/${JOBNAMEREDUX}/ date; rsync -arzq --delete ${STAGINGDIR}/* $DESTINATION/builds/nightly/${JOBNAMEREDUX}/${BUILD_ID}-H${BUILD_NUMBER}/ fi rm -f /tmp/latestBuild.html {code} was (Author: nickboldt): Currently, we do this. Fairly straightforward. Works on all mirrors (download.jboss, www.qa, and the Brno server): echo "<meta http-equiv=\"refresh\" content=\"0;url=${BUILD_ID}-H${BUILD_NUMBER}/\">" > /tmp/latestBuild.html if [[ ${PUBLISHPATHSUFFIX} ]]; then date; rsync -arzq --delete ${STAGINGDIR}/* $DESTINATION/builds/nightly/${PUBLISHPATHSUFFIX}/${BUILD_ID}-H${BUILD_NUMBER}/ date; rsync -arzq --delete /tmp/latestBuild.html $DESTINATION/builds/nightly/${PUBLISHPATHSUFFIX}/ else date; rsync -arzq --delete /tmp/latestBuild.html $DESTINATION/builds/nightly/${JOBNAMEREDUX}/ date; rsync -arzq --delete ${STAGINGDIR}/* $DESTINATION/builds/nightly/${JOBNAMEREDUX}/${BUILD_ID}-H${BUILD_NUMBER}/ fi rm -f /tmp/latestBuild.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9266?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-9266: ----------------------------------- https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/3216/ pending to test this out. Look here to see if link appears correctly and works: http://download.jboss.org/jbosstools/builds/nightly/trunk/latest/ -> should point at H3216 build, not current H3211 build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9266?page=com.atlassian.jira.plugin... ] 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@server: prefix, use "hudson@`hostname -f`:/path/to/put/files" instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9266?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9266: -------------------------------------------- why not just use rsync with --links as suggested ? that should work no matter if its local or remote ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9266?page=com.atlassian.jira.plugin... ] Nick Boldt edited comment on JBIDE-9266 at 7/28/11 10:02 AM: ------------------------------------------------------------- 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: {code} -a, --archive archive mode; equals -rlptgoD (no -H,-A,-X) -l, --links copy symlinks as symlinks {code} HOWEVER, this won't solve the "move folders & delete others over sftp" that I'm using in JBIDE-8667. was (Author: nickboldt): 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 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira