[richfaces-planning-issues] [JBoss JIRA] Resolved: (RFPL-458) Review, update, clean richfaces hudson builds from internal server

[Jay Balunas (JIRA)]

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

Jay Balunas resolved RFPL-458.
------------------------------

    Resolution: Done


Finished review of the new hudson views, and shifted around various builds.  Between this effort and the efforts of Lukas I think the Richfaces hudson views are in good shape.  There is still some stabilization work required in RF-3.3, but other views are as they should be.

> Review, update, clean richfaces hudson builds from internal server
> ------------------------------------------------------------------
>
>                 Key: RFPL-458
>                 URL: https://jira.jboss.org/jira/browse/RFPL-458
>             Project: RichFaces Planning
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: administration, build, QA, site
>            Reporter: Jay Balunas
>            Assignee: Jay Balunas
>            Priority: Critical
>             Fix For: 4.0.0.ALPHA2
>
>
> We have updated the hudson for RichFaces and created the following views.  During this review there were many RichFaces builds that we not completed, or abandoned.
> http://hudson.qa.jboss.com/hudson/view/RF-3.3/
> http://hudson.qa.jboss.com/hudson/view/RF-4.0/
> http://hudson.qa.jboss.com/hudson/view/RF-Int/
> http://hudson.qa.jboss.com/hudson/view/RF-Prod/
> http://hudson.qa.jboss.com/hudson/view/RF-QE/
> http://hudson.qa.jboss.com/hudson/view/RF-Rel/
> These builds need to be reviewed, cleaned, removed, etc... as needed.  The goal is that every build in RF-3.3, RF-4.0, RF-Prod be builds that we can rely on for accurate information on status.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira