ideas:buildbot

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
ideas:buildbot [2009/05/02 16:27]
philip moved from gsoc 2009, added progress/status
ideas:buildbot [2009/08/27 10:51]
dabase Added 2 build types
Line 5: Line 5:
  
 The back end should attempt to build the resulting configurations,​ push any binaries/​log files to a server and email the requester with the location/​status of the finished build product. The back end should attempt to build the resulting configurations,​ push any binaries/​log files to a server and email the requester with the location/​status of the finished build product.
 +
 +===== Possible Build Scenarios =====
 +There are different Build Scenarios that need to be executed by a automated build bot. The main goal should be providing fast informations for developers wheter a build works or not on a specific system/​distro. It's important to get this information spread fast.
 +
 +==== Minimal Build ====
 +  * Has a Minimum extensions activated and just covers the core features of php. 
 +  * Is supposed to run very fast (< 20 Minutes) ​
 +  * Runs on every new SVN revision
 +  * No Coverage (main goal is minimizing build time) 
 +
 +==== Full Build ====
 +  * Has as much as possible extentions activated ​
 +  * Is supposed to run complete
 +  * Main reason is to check if there are tests broken in the big picture
 +  * Runs timed (once a day?) 
 +
 +==== Coverage and Grind build ====
 +  * Generate Valgrind Reports and report overall failed tests
 +  * Maybe run n special boxes ?
 +
 +==== Extension level build with coverage ====
 +  * PHP Core and One Extension is tested
 +  * With Coverage ​
 +  * Triggered once a day
 +
 +==== Extension Level Builds without coverage ====
 +  * Triggered on checkin on this extension
  
 ==== Progress ==== ==== Progress ====
ideas/buildbot.txt · Last modified: 2017/09/22 13:28 (external edit)