pear:qa:ci
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| pear:qa:ci [2010/09/09 00:32] – clockwerx | pear:qa:ci [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| http:// | http:// | ||
| * [[http:// | * [[http:// | ||
| - | * [[http:// | + | |
| - | * [[http://test.pear.php.net: | + | |
| + | * [[https://github.com/pear/pear-svn-git|Migrate to github script]] | ||
| - | The helper scripts live at http://svn.php.net/ | + | The helper scripts live at https://github.com/ |
| - | ===== Cruise Control | + | ===== Jenkins |
| - | Cruise Control | + | Jenkins |
| - | The build task does: | + | ==== Access === |
| - | - Update svn | + | Jenkins |
| - | - Run '' | + | |
| - | - Run '' | + | |
| - | - Run '' | + | |
| - | - Run '' | + | |
| - | - Run '' | + | |
| - | - Build the package with Pyrus | + | |
| - | If either the unit tests or building the package | + | ==== Adding a new job/build ==== |
| - | + | * Create job | |
| - | A file, called trunk.tar.gz is created as a build artifact. | + | * Enter package |
| + | * Enter link to github | ||
| + | * Enter the read-only git url into source management | ||
| + | * Select 'build on push from github' | ||
| + | * Add either manual build steps or invoke an ant build.xml target. Manual steps should include executing | ||
| + | * phpunit --coverage-html | ||
| + | * php ~/ | ||
| + | * Add in Post-build Actions for ' | ||
| ==== How do I make sure my tests work? ==== | ==== How do I make sure my tests work? ==== | ||
| - | In general, we encourage the use of an AllTests.php - we target PHPUnit 3.4 at this time. | + | In general, we encourage the use of an appropriate phpunit.xml - we target PHPUnit 3.6 at this time. |
| - | Your package directory layout should allow you to successfully run your test suite as below: | + | Your package directory layout should allow you to successfully run your test suite as below (assuming svn): |
| <code bash> | <code bash> | ||
| $ cd Foo_Bar/ | $ cd Foo_Bar/ | ||
| - | $ php tests/AllTests.php | + | $ phpunit -c phpunit.xml |
| </ | </ | ||
| - | The continuous integration box does this slightly differently: | + | |
| + | ==== My directory layout doesn' | ||
| + | A common pattern with older packages is to have a directory structure which is unlike the installed package layout. IE: '' | ||
| + | |||
| + | To fix this: | ||
| + | <code bash> | ||
| + | $ svn mkdir Foo | ||
| + | $ svn mv Bar.php Foo/ | ||
| + | # Edit package.xml, | ||
| + | $ vim package.xml | ||
| + | |||
| + | # Rebuild package using PEAR_PackageFileManager_CLI | ||
| + | $ pfm | ||
| + | |||
| + | # Run tests to confirm no fatal errors, using one of | ||
| + | $ pear run-tests -r tests/ | ||
| + | $ phpunit tests/ | ||
| + | |||
| + | # Commit | ||
| + | $ svn commit -m " | ||
| + | </ | ||
| + | |||
| + | ==== Pyrus won't build my package 1.0 ==== | ||
| + | See [[pear: | ||
| + | |||
| + | ==== My unit tests need a (database/ | ||
| + | Two strategies exist for this: | ||
| + | - Making use of PHPUnit' | ||
| + | - Checking your environment and skipping the test if it cannot run | ||
| + | |||
| + | There is also a test mysql instance available. | ||
| + | |||
| + | > Hi Daniel: | ||
| + | > | ||
| + | > On Wed, Nov 16, 2011 at 08:34:04AM +1030, Daniel O' | ||
| + | > > http:// | ||
| + | > > | ||
| + | > > This and a few others obviously need a database to be tested properly. | ||
| + | > > Certainly that machine has mysql on it; or sqlite is probably available - | ||
| + | > > what would be needed to load up an appropriate schema/tear it down after | ||
| + | > > the tests? | ||
| + | > | ||
| + | > I agree and mentioned this on pear-qa a while ago. Take a look at what | ||
| + | > I committed to DB tests yesterday. | ||
| + | > MYSQL_TEST_* environment variables, which are used for PHP's tests. | ||
| + | > should create a test user and database and set those environment | ||
| + | > variables in the cron job, or whatever. | ||
| + | > | ||
| + | > A similar setup should be made for PostgreSQL in PEAR and PHP's unit | ||
| + | > tests. | ||
| + | > | ||
| + | > SQLite3 tests should use ": | ||
| + | > | ||
| + | > Thanks, | ||
| + | > | ||
| + | > --Dan | ||
| + | |||
| + | ==== Build tools ==== | ||
| + | In general, ant is the preferred way of managing a build after a certain level of complexity. See http:// | ||
| + | |||
| + | Noteably, we prefer phpdoc/ | ||
| + | |||
| + | Some packages use phing | ||
| + | |||
| + | ==== Dependencies ==== | ||
| + | There are two available techniques for managing dependencies without installing system wide libraries. | ||
| + | |||
| + | The first is relatively straight forward - simply pulling the library from source and pushing it into a lib directory. | ||
| + | <code bash> | ||
| + | $ git clone git:// | ||
| + | $ git clone git:// | ||
| + | $ phpunit --include-path lib/ | ||
| + | </ | ||
| + | |||
| + | This can be either configured in the jenkins build or (preferred) in the relevant build.xml and phpunit.xml files. | ||
| + | |||
| + | |||
| + | The second is to utilise [[http:// | ||
| ==== Todo ==== | ==== Todo ==== | ||
| - | - Fix how pear2-packages-all and pear2/all relate to the test suite | + | - Put more packages |
| - | - Generate a changelog, package.xml file (possibly in pearweb, possible on the command line) automatically; | + | |
| - | - Investigate what's up with the Metrics and other Cruise Control errors | + | |
| - Investigate a notification task to package maintainers? | - Investigate a notification task to package maintainers? | ||
| - Investigate allowing bootstrapped build.xml files back in (Pyrus) | - Investigate allowing bootstrapped build.xml files back in (Pyrus) | ||
| Line 49: | Line 126: | ||
| Before releasing a new version of PEAR, we need to make sure it runs on as many systems as possible. It's pretty easy: | Before releasing a new version of PEAR, we need to make sure it runs on as many systems as possible. It's pretty easy: | ||
| - | - Install the new PEAR (1.7.0RC2 currently) | + | - Install the new PEAR |
| - Make sure you have the XML_RPC package | - Make sure you have the XML_RPC package | ||
| - | - Checkout pear-core from CVS to get the tests | + | - Checkout pear-core from the repository |
| - Run the tests | - Run the tests | ||
| Line 57: | Line 134: | ||
| pear upgrade -f PEAR | pear upgrade -f PEAR | ||
| pear upgrade XML_RPC | pear upgrade XML_RPC | ||
| - | cvs -d :pserver: | + | git clone git://github.com/pear/pear-core.git |
| cd pear-core/ | cd pear-core/ | ||
| </ | </ | ||
| Line 69: | Line 146: | ||
| * For some tests the executable php-cgi is needed. In some Linux distributions this is contained in a separate package, but on for instance Gentoo Linux this has to be enabled using the cgi USE flag. | * For some tests the executable php-cgi is needed. In some Linux distributions this is contained in a separate package, but on for instance Gentoo Linux this has to be enabled using the cgi USE flag. | ||
| * If running on linux, do not run the tests as root | * If running on linux, do not run the tests as root | ||
| - | |||
| - | |||
pear/qa/ci.1283992342.txt.gz · Last modified: 2017/09/22 13:28 (external edit)