Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "COSMOS BUILD SCHEDULE"

(New page: == COSMOS Build Schedule == == Weekly integration builds == {| style="text-align:left" border="1" |+ <h3>Build schedule</h3> |- style="background: #f2f2f2;" ! !! Monday !! Tuesday !! Wed...)
 
Line 1: Line 1:
 
== COSMOS Build Schedule ==
 
== COSMOS Build Schedule ==
  
== Weekly integration builds ==
+
== Weekly integration builds schedule ==
 
{| style="text-align:left" border="1"
 
{| style="text-align:left" border="1"
|+ <h3>Build schedule</h3>
 
 
|- style="background: #f2f2f2;"  
 
|- style="background: #f2f2f2;"  
 
! !! Monday !! Tuesday !! Wednesday !! Thursday !! Friday
 
! !! Monday !! Tuesday !! Wednesday !! Thursday !! Friday
 
|-
 
|-
 
!  9:00 AM
 
!  9:00 AM
|  ||  || Post the candidate weekly integration build on the downloads page. Build team to post an email to cosmos-dev to notify development that the JUnits can begin. || ||
+
|  ||  ||  
 +
* Post the candidate weekly integration build on the downloads page.  
 +
* Build team to post an email to cosmos-dev to notify development that the JUnits can begin.
 +
|| ||
 
|-
 
|-
 
! 12:00 PM
 
! 12:00 PM
|  ||  || Development posts the results of the project JUnits to the cosmos-dev mailing list. (Note: this is not the TPTP JUnits due to time constraints. JUnits are to be run on Windows only.) || ||
+
|  ||  ||  
 +
* Development posts the results of the project JUnits to the cosmos-dev mailing list. (Note: this is not the TPTP JUnits due to time constraints. JUnits are to be run on Windows only.)  
 +
|| ||
 
|-
 
|-
 
! 1:00 PM
 
! 1:00 PM
|  || Finish reviewing all patches from bugzilla. Check in if the patch passes review. || If all JUnit results good, promote the candidate build to the official weekly build on the download page. Build team to send a email to cosmos-dev notifying QA to pick up the build at this time. || ||  
+
|  ||  
 +
* Finish reviewing all patches from bugzilla. Check in the patch if it passes review.  
 +
||  
 +
* If all JUnit results good, promote the candidate build to the official weekly build on the download page.  
 +
* Once the candidate build is promoted, Build team to send a email to cosmos-dev notifying QA to pick up the build at this time.  
 +
|| ||  
 
|-
 
|-
 
! 3:59 PM
 
! 3:59 PM
| Attach all patches in bugzilla || Finish checking in all code for the weekly integration build ||  || ||
+
|  
 +
* Attach all patches in bugzilla  
 +
||  
 +
* Finish checking in all code for the weekly integration build  
 +
||  || ||
 
|-  
 
|-  
 
! 4:00 PM
 
! 4:00 PM
| || Build starts || || ||  
+
| || <h3>Build starts</h3> || || ||  
 
|}
 
|}

Revision as of 12:37, 4 February 2008

COSMOS Build Schedule

Weekly integration builds schedule

Monday Tuesday Wednesday Thursday Friday
9:00 AM
  • Post the candidate weekly integration build on the downloads page.
  • Build team to post an email to cosmos-dev to notify development that the JUnits can begin.
12:00 PM
  • Development posts the results of the project JUnits to the cosmos-dev mailing list. (Note: this is not the TPTP JUnits due to time constraints. JUnits are to be run on Windows only.)
1:00 PM
  • Finish reviewing all patches from bugzilla. Check in the patch if it passes review.
  • If all JUnit results good, promote the candidate build to the official weekly build on the download page.
  • Once the candidate build is promoted, Build team to send a email to cosmos-dev notifying QA to pick up the build at this time.
3:59 PM
  • Attach all patches in bugzilla
  • Finish checking in all code for the weekly integration build
4:00 PM

Build starts

Back to the top