[ https://issues.jboss.org/browse/JBBUILD-720?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBBUILD-720: ------------------------------------ You can achieve this with some shell script at the end of your publishing job in Jenkins. Note that I use "updates/" in the paths, not "update/" (as documented above) because there will invariably be more than 1 in there. :) Also, our convention is "development/" in place of "develop/", as it's a development milestone update (noun), not a place from which to develop an update (verb). {code} ECLIPSERELEASE=indigo PROJECTNAME=modeshape RELEASETYPE=stable; # can also be 'development' or 'nightly' PROJECTVERSION=1.2.3.Final; # or 2.3.4.M5 or whatever you release is called SOURCESERVER=tools@filemgmt.jboss.org:/downloads_htdocs # if in Jenkins can use SOURCEPATH=/modeshape/builds/staging/${JOB_NAME}/all/repo to make this script more cross-job portable SOURCEPATH=/modeshape/builds/staging/modeshape-tools-continuous/all/repo DESTINATION=tools@filemgmt.jboss.org:/downloads_htdocs/tools/updates/${RELEASETYPE}/${ECLIPSERELEASE}/soa-tooling # if folder already exists, sftp will throw an error but should still be able to proceed echo "mkdir ${PROJECTNAME}" | sftp ${DESTINATION} # symlinking appears to only works with relative paths echo "ln ../../../../../..${SOURCEPATH}/${PROJECTVERSION}/org.drools.updatesite ${PROJECTVERSION}" | sftp ${DESTINATION}/${PROJECTNAME}/ echo "Click here: http://download.jboss.org/jbosstools/updates/${RELEASETYPE}/${ECLIPSERELE... {code} Alternatively, instead of symlink, could also fetch from one site & post to the other (uses twice as much disk space, however) {code} rsync -aPz --rsh=ssh --protocol=28 ${SOURCESERVER}${SOURCEPATH}/${PROJECTVERSION}/org.drools.updatesite/* /tmp/org.drools.updatesite-${PROJECTVERSION} rsync -aPz --rsh=ssh --protocol=28 --delete /tmp/org.drools.updatesite-${PROJECTVERSION}/* ${DESTINATION}/${PROJECTNAME}/${PROJECTVERSION}/ # cleanup rm -fr /tmp/org.drools.updatesite-${PROJECTVERSION} echo "Click here: http://download.jboss.org/jbosstools/updates/${RELEASETYPE}/${ECLIPSERELE... {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-720?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBBUILD-720 at 8/28/12 5:24 PM: ------------------------------------------------------------- You can achieve this with some shell script at the end of your publishing job in Jenkins. Note that I use "updates/" in the paths, not "update/" (as documented above) because there will invariably be more than 1 in there. :) Also, our convention is "development/" in place of "develop/", as it's a development milestone update (noun), not a place from which to develop an update (verb). {code} ECLIPSERELEASE=indigo PROJECTNAME=modeshape RELEASETYPE=stable; # can also be 'development' or 'nightly' PROJECTVERSION=1.2.3.Final; # or 2.3.4.M5 or whatever you release is called SOURCESERVER=tools@filemgmt.jboss.org:/downloads_htdocs # if in Jenkins can use SOURCEPATH=/modeshape/builds/staging/${JOB_NAME}/all/repo to make this script more cross-job portable SOURCEPATH=/modeshape/builds/staging/modeshape-tools-continuous/all/repo DESTINATION=tools@filemgmt.jboss.org:/downloads_htdocs/tools/updates/${RELEASETYPE}/${ECLIPSERELEASE}/soa-tooling # if folder already exists, sftp will throw an error but should still be able to proceed echo "mkdir ${PROJECTNAME}" | sftp ${DESTINATION} # symlinking appears to only works with relative paths echo "ln ../../../../../..${SOURCEPATH}/ ${PROJECTVERSION}" | sftp ${DESTINATION}/${PROJECTNAME}/ echo "Click here: http://download.jboss.org/jbosstools/updates/${RELEASETYPE}/${ECLIPSERELE... {code} Alternatively, instead of symlink, could also fetch from one site & post to the other (uses twice as much disk space, however) {code} rsync -aPz --rsh=ssh --protocol=28 ${SOURCESERVER}${SOURCEPATH}/* /tmp/updatesite-${PROJECTVERSION} rsync -aPz --rsh=ssh --protocol=28 --delete /tmp/updatesite-${PROJECTVERSION}/* ${DESTINATION}/${PROJECTNAME}/${PROJECTVERSION}/ # cleanup rm -fr /tmp/updatesite-${PROJECTVERSION} echo "Click here: http://download.jboss.org/jbosstools/updates/${RELEASETYPE}/${ECLIPSERELE... {code} was (Author: nickboldt): You can achieve this with some shell script at the end of your publishing job in Jenkins. Note that I use "updates/" in the paths, not "update/" (as documented above) because there will invariably be more than 1 in there. :) Also, our convention is "development/" in place of "develop/", as it's a development milestone update (noun), not a place from which to develop an update (verb). {code} ECLIPSERELEASE=indigo PROJECTNAME=modeshape RELEASETYPE=stable; # can also be 'development' or 'nightly' PROJECTVERSION=1.2.3.Final; # or 2.3.4.M5 or whatever you release is called SOURCESERVER=tools@filemgmt.jboss.org:/downloads_htdocs # if in Jenkins can use SOURCEPATH=/modeshape/builds/staging/${JOB_NAME}/all/repo to make this script more cross-job portable SOURCEPATH=/modeshape/builds/staging/modeshape-tools-continuous/all/repo DESTINATION=tools@filemgmt.jboss.org:/downloads_htdocs/tools/updates/${RELEASETYPE}/${ECLIPSERELEASE}/soa-tooling # if folder already exists, sftp will throw an error but should still be able to proceed echo "mkdir ${PROJECTNAME}" | sftp ${DESTINATION} # symlinking appears to only works with relative paths echo "ln ../../../../../..${SOURCEPATH}/${PROJECTVERSION}/org.drools.updatesite ${PROJECTVERSION}" | sftp ${DESTINATION}/${PROJECTNAME}/ echo "Click here: http://download.jboss.org/jbosstools/updates/${RELEASETYPE}/${ECLIPSERELE... {code} Alternatively, instead of symlink, could also fetch from one site & post to the other (uses twice as much disk space, however) {code} rsync -aPz --rsh=ssh --protocol=28 ${SOURCESERVER}${SOURCEPATH}/${PROJECTVERSION}/org.drools.updatesite/* /tmp/org.drools.updatesite-${PROJECTVERSION} rsync -aPz --rsh=ssh --protocol=28 --delete /tmp/org.drools.updatesite-${PROJECTVERSION}/* ${DESTINATION}/${PROJECTNAME}/${PROJECTVERSION}/ # cleanup rm -fr /tmp/org.drools.updatesite-${PROJECTVERSION} echo "Click here: http://download.jboss.org/jbosstools/updates/${RELEASETYPE}/${ECLIPSERELE... {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-720?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBBUILD-720 at 8/28/12 5:28 PM: ------------------------------------------------------------- Note too that in your job (https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/modeshape-tools-cont...), you could even just replace the call to publish.sh: {code} mkdir -p ${WORKSPACE}/build/publish cd ${WORKSPACE}/build/publish rm -f ${WORKSPACE}/build/publish/publish.sh wget http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x/build... export DESTINATION="modeshape@filemgmt.jboss.org:/downloads_htdocs/modeshape" . ${WORKSPACE}/build/publish/publish.sh tools/tmp {code} ... with a script like the one above, but which would take as input this folder instead of a remote one: {code}${WORKSPACE}/sources/site/target/repository/{code} and could therefore do this: {code} RELEASETYPE=stable; # can also be 'development' or 'nightly' ECLIPSERELEASE=indigo PROJECTNAME=modeshape-tools PROJECTVERSION=1.2.3.Final; # or 2.3.4.M5 or whatever you release is called DESTINATION=tools@filemgmt.jboss.org:/downloads_htdocs/tools/updates/${RELEASETYPE}/${ECLIPSERELEASE}/soa-tooling # if folder already exists, sftp will throw an error but should still be able to proceed echo "mkdir ${PROJECTNAME}" | sftp ${DESTINATION} rsync -aPz --rsh=ssh --protocol=28 ${WORKSPACE}/sources/site/target/repository/* ${DESTINATION}/${PROJECTNAME}/${PROJECTVERSION}/ echo "Update site is http://download.jboss.org/jbosstools/updates/${RELEASETYPE}/${ECLIPSERELE... {code} was (Author: nickboldt): Note too that in your job (https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/modeshape-tools-cont...), you could even just replace the call to publish.sh: {code} mkdir -p ${WORKSPACE}/build/publish cd ${WORKSPACE}/build/publish rm -f ${WORKSPACE}/build/publish/publish.sh wget http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x/build... export DESTINATION="modeshape@filemgmt.jboss.org:/downloads_htdocs/modeshape" . ${WORKSPACE}/build/publish/publish.sh tools/tmp {code} ... with a script like the one above, but which would take as input this folder instead of a remote one: {code}${WORKSPACE}/sources/site/target/repository/{code} and could therefore do this: {code} RELEASETYPE=stable; # can also be 'development' or 'nightly' ECLIPSERELEASE=indigo PROJECTNAME=modeshape-tools PROJECTVERSION=1.2.3.Final; # or 2.3.4.M5 or whatever you release is called DESTINATION=tools@filemgmt.jboss.org:/downloads_htdocs/tools/updates/${RELEASETYPE}/${ECLIPSERELEASE}/soa-tooling # if folder already exists, sftp will throw an error but should still be able to proceed echo "mkdir ${PROJECTNAME}" | sftp ${DESTINATION} rsync -aPz --rsh=ssh --protocol=28 ${WORKSPACE}/sources/site/target/repository/* ${DESTINATION}/${PROJECTNAME}/${PROJECTVERSION}/ {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-720?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBBUILD-720: ---------------------------------- Assignee: Dan Florian (was: Nick Boldt) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-720?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBBUILD-720: ------------------------------------ If the goal here is to drive the parameters into the job and thus into the script, you can do so like this: a) log into Jenkins, then configure the job. b) check the box for "This build is parameterized". c) set a String Parameter called TARGETPATHROOT. d) set the default value to "modeshape@filemgmt.jboss.org:/downloads_htdocs/modeshape/tools/updates/development/juno/3.3.0.Beta5/" (You could drive it from multiple parameters like in your example, but since it's just you running it, that seems unnecessary.) Then to publish, just do this via an Execute shell block in the jobs: {code} cd ${WORKSPACE}/sources/ wget http://anonsvn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh -q --no-check-certificate -N DESTINATION=${TARGETPATHROOT} . publish.sh tools/tmp {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira