internals:buildbot
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| internals:buildbot [2009/10/06 20:54] – Added rough draft for continuous integration implementation iekpo | internals:buildbot [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 40: | Line 40: | ||
| Here is the rough draft for the implementation details: | Here is the rough draft for the implementation details: | ||
| + | Please contact me at iekpo@php.net if you have any questions, comments or recommendations. | ||
| ==== 0. Target Subversion URLs ==== | ==== 0. Target Subversion URLs ==== | ||
| Line 48: | Line 49: | ||
| So the build bot will only be monitoring commits to the following subversion URLS : | So the build bot will only be monitoring commits to the following subversion URLS : | ||
| - | PHP 5.3: http:// | + | * PHP 5.3: https:// |
| - | PHP 5.2: http:// | + | |
| - | PHP 6: http:// | + | |
| A separate build daemon will be set up for each branch on each UNIX server. | A separate build daemon will be set up for each branch on each UNIX server. | ||
| Line 80: | Line 81: | ||
| Here are the states : | Here are the states : | ||
| - | 2A : The source code will be checked out of SVN. | + | * 2A : The source code will be checked out of SVN. |
| - | 2B : Then the buildconf command will be run. | + | |
| - | 2C : Then the configure script will be run will all the extensions enabled. | + | |
| - | 2D : Then make | + | |
| - | 2E : Then make install | + | |
| If any of the above steps fail, this particular job is put on HOLD and an email notification will be sent out. | If any of the above steps fail, this particular job is put on HOLD and an email notification will be sent out. | ||
| - | 2F : Then make test (or any other simpler alternative) | + | * 2F : Then make test (or any other simpler alternative) |
| - | 2G: The results will then be agregated an analyzed. This will be explained in 4 below | + | * 2G: The results will then be agregated an analyzed. This will be explained in 4 below |
| However, we have to take care of the following cases/ | However, we have to take care of the following cases/ | ||
| - | 1. Removal of phpt scripts (a phpt script that was in the previous revision no longer exists) | + | * 1. Removal of phpt scripts (a phpt script that was in the previous revision no longer exists) |
| - | 2. Addition of new phpt scripts (a phpt script that never existed is now introduced) | + | |
| Line 110: | Line 111: | ||
| ==== 4. Intepretation of Build results ==== | ==== 4. Intepretation of Build results ==== | ||
| - | 2G1 : Existing phpt files. | + | 2G1 : Existing phpt files |
| - | If the result changes from PASS to FAIL, a FAILURE notice will be sent out (RED) | + | |
| - | If the result changes from FAIL to PASS, a RESTORED notice will be sent out (GREEN) | + | |
| - | If the result remains at PASS, no notice will be sent out. | + | |
| - | If the result remains at FAIL, no notice will be sent out. | + | |
| - | 2G1 : Removed phpt files. | + | * If the result changes from PASS to FAIL, a FAILURE notice will be sent out (RED) |
| + | * If the result changes from FAIL to PASS, a RESTORED notice will be sent out (GREEN) | ||
| + | * If the result remains at PASS, no notice will be sent out. | ||
| + | * If the result remains at FAIL, no notice will be sent out. | ||
| + | |||
| + | 2G2 : Removed phpt files. | ||
| A REMOVED notice will be sent out (ORANGE) | A REMOVED notice will be sent out (ORANGE) | ||
| - | 2G1 : Newly introduced phpt files. | + | 2G3 : Newly introduced phpt files. |
| - | If the result is FAIL, a FAILURE notice will be sent out (RED) | + | |
| - | If the result is PASS, a PASS notice will be sent out (GREEN) | + | |
| ==== 5. Managing Results Data ==== | ==== 5. Managing Results Data ==== | ||
internals/buildbot.1254862449.txt.gz · Last modified: 2017/09/22 13:28 (external edit)