Your SlideShare is downloading. ×
  • Like
Hudson Continuous Integration for PHP
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Hudson Continuous Integration for PHP

  • 4,776 views
Published

Presentation given at BarCamp Blackpool as a precursor to a practical demonstration of Hudson, Phing, PHPUnit etc.

Presentation given at BarCamp Blackpool as a precursor to a practical demonstration of Hudson, Phing, PHPUnit etc.

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • Presentation given at BarCamp Blackpool as a precursor to a practical demonstration of Hudson, Phing, PHPUnit etc.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
4,776
On SlideShare
0
From Embeds
0
Number of Embeds
3

Actions

Shares
Downloads
75
Comments
1
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Hudson for PHP
  • 2. Jeremy Coates MD Magma Digital Ltd Founder PHPNW @phpcodemonkey
  • 3. Continuous Integration? Regular build / deployment of code Enables automated documentation building, testing, style checking Dashboard / control panel to monitor state Related to Unit Testing & other Agile development practices
  • 4. Why CI? Improve quality of code, across development teams. Open development, good peer pressure Ensure consistency of style, reduce maintenance cycle overheads Remove human nature laziness, it's automatic! Prove it builds & deploys regularly, shorter development cycle
  • 5. Why CI? /cont Each developer integrates at least daily Those integrations are verified by the CI build job Issues are reported after the build, opportunity to make right in short time span
  • 6. Why CI? /cont Automate the hard / boring build steps Risk management Deployment automated, at least every day Visibilty increases across development team Confidence in build and software quality increased
  • 7. Workflow Developer commits code to VCS CI Server detects changes CI Server checks out / updates code, runs tests, analyses code CI Server feeds back to development team
  • 8. CI Servers Bamboo Cruise Control (phpUnderControl) Hudson Own Scripts, linking tools
  • 9. http://hudson-ci.org/
  • 10. More Resources http://www.davegardner.me.uk/blog/ 2009/11/09/continuous-integration-for-php- using-hudson-and-phing/ http://www.phpunit.de/manual/current/en/ continous-integration.html http://cruisecontrol.sf.net/ http://www.phpundercontrol.org/ http://www.atlassian.com/software/bamboo/
  • 11. Jeremy Coates MD Magma Digital Ltd Founder PHPNW @phpcodemonkey