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

Wed Mar 13 03:47:41 EDT 2013

     [ https://issues.jboss.org/browse/JBIDE-12973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mickael Istria updated JBIDE-12973:
-----------------------------------

    Assignee: Martin Malina  (was: Nick Boldt)

> The maven build finishes, but there is a problem with publishing at the end: ERROR: Publisher hudson.tasks.Mailer aborted due to exception

Yes, it issue JBIDE-13040 . As a workaround you should disable "Send separate e-mails to individuals who broke the build"

> BTW, I was wondering why it has so many failures when the same build is clean here (except for windows):

Maybe you're missing a window manager (which is necessary for SWTBot stuff when it comes to dealing with menus, maybe it's the same for RedDeer and Eclipse in general). Try adding this to add an initial shell script with "metacity --sm-disable --replace &"

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