[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=12714395#comment-12714395 ] 

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-continuous/configure), 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/publish/publish.sh
export DESTINATION="modeshape at 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 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}

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}/${ECLIPSERELEASE}/soa-tooling/${PROJECTNAME}/${PROJECTVERSION}/"
{code}
                
      was (Author: nickboldt):
    Note too that in your job (https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/modeshape-tools-continuous/configure), 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/publish/publish.sh
export DESTINATION="modeshape at 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 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}

rsync -aPz --rsh=ssh --protocol=28 ${WORKSPACE}/sources/site/target/repository/* ${DESTINATION}/${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