[jboss-jira] [JBoss JIRA] (JBBUILD-720) Change modeshape-tools-continuous Jenkins Job Update-Site Output Directory

[Nick Boldt (JIRA)]

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

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 at 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 at 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}/${ECLIPSERELEASE}/soa-tooling/${PROJECTNAME}/${PROJECTVERSION}"
{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}/${ECLIPSERELEASE}/soa-tooling/${PROJECTNAME}/${PROJECTVERSION}"
{code}
                
> Change modeshape-tools-continuous Jenkins Job Update-Site Output Directory
> --------------------------------------------------------------------------
>
>                 Key: JBBUILD-720
>                 URL: https://issues.jboss.org/browse/JBBUILD-720
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven Builds
>    Affects Versions: Build Support 2011
>            Reporter: Dan Florian
>            Assignee: Nick Boldt
>
> The modeshape-tools-continuous job outputs the ModeShape Tools update-site to here:
> /downloads_htdocs/modeshape/builds/staging/modeshape-tools-continuous/all/repo
> We would like the path to be (something like) this:
> /downloads_htdocs/modeshape/tools/update/{stable|develop}/{helios|indigo|juno|etc}
> At a minimum, the path needs to have the "tools" segment as this identifies it from the ModeShape project. What do other projects do as far as stable vs. develop build? Do other project's put the Eclipse release in the path? Please see MODE-1506 for additional questions/discussion.
> I was told to get with you on this Nick. Please update this issue's project and component as appropriate as I wasn't sure.

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