[jbosstools-issues] [JBoss JIRA] (JBIDE-12973) publish reddeer update site to download.jboss.org

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-12973:
---------------------------------------

Thanks Nick, this seems to work. So the next step for me is to remove repo definitions from all the tests and have just one repo defined in our root pom. For now it is the master nightly build, but of course the idea was that we always point to some specific build so that will be the next step.
I tried using your promote job to create this:
http://download.jboss.org/jbosstools/updates/integration/kepler/core/reddeer/0.2.0.Final/

This was just a first attempt. At first I thought that the job will also ask for a version and then change the feature version but I guess I was wrong - so we need to have all the correct versions already in the builds before we promote that build, right?

What path would you suggest I use in the future? Except for the version (the last part), is the above ok? Next time maybe I should use something like 0.2.0.201301271221 to reflect the exact snapshot?
                
> publish reddeer update site to download.jboss.org
> -------------------------------------------------
>
>                 Key: JBIDE-12973
>                 URL: https://issues.jboss.org/browse/JBIDE-12973
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng, testing, updatesite
>    Affects Versions: 4.0.0.Beta2
>            Reporter: Nick Boldt
>            Assignee: Martin Malina
>             Fix For: 4.1.x
>
>
> Red deer should publish nightly/development/stable update sites like other components of JBT onto download.jboss.org.
> Simplest way to get a nightly build into download.jboss.org/jbosstools/builds/staging/ is to use my publish.sh [1] script as a step during your build job.
> Then, if you want to copy that to a more stable URL (for a dev milestone or stable release) use this job [2]:
> [1] https://svn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/

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