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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-12973:
------------------------------------

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/RedDeer_master/2/console is running but is having permgen issues. Maybe it needs more memory? 

Assuming that it completes and most of the tests are OK, you should get:

* test output
* jacoco coverage report
* archived artifacts
* published results here: http://download.jboss.org/jbosstools/builds/staging/RedDeer_master

Then, when you decide you want to copy a nightly build as an integration build, dev milestone, or stable release, you can run https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/ to perform the copy.

                
> 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: Nick Boldt
>             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