News Feed
Jobs Feed
Sections




News Archive
feed this:

Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

SensioLabs Insight Blog:
Jenkins integration
March 13, 2014 @ 09:06:25

The latest post to the SensioLabs Insight blog today shows you how you can integrate the service with Jenkins as a part of your pre-existing continuous integration workflow.

One of the main features of SensioLabsInsight service is that it integrates smoothly into your existing workflow and technical infrastructure. We know that most companies use Jenkins as their continuous integration server and for that reason, SensioLabsInsight provides out-of-the-box Jenkins integration.

The integration uses the Insight API to perform the checks and return a report of the results. They step you through the process to get the connection set up (using the API client) and send the request for processing. The result is returned in PMD format, something Jenkins can easily parse and integrate into the pass/fail of the job. You can also get the details of the issues including error message, file location and the priority of the issue.

0 comments voice your opinion now!
jenkins continuous integration sensiolabs insight

Link: http://blog.insight.sensiolabs.com/2014/02/12/jenkins-integration.html

David Adams:
Zero to Jenkins - PHP Continuous Integration
September 27, 2013 @ 12:15:27

David Adams has posted another screencast to YouTube, this time it's about setting up Jenkins for continuous integration in a PHP-based application. (His previous one about using PHP on Digital Ocean is here).

The tutorial walks you through the entire process, including creating the Vagrant configuration:

  • Installing Jenkins via apt-get
  • Setting up the commands needed to run jobs
  • Configuring it to work with a Bitbucket project
  • Installing plugins/upgrades
  • Security configuration

He also shows some of the results of the job executions, both passing and failing. The video's about 50 minutes long, so it's not a quick installation but it is detailed.

0 comments voice your opinion now!
jenkins screencast continuous integration screencast tutorial

Link: https://www.youtube.com/watch?v=PklYO2vYIfc

SitePoint PHP Blog:
Continuous Deployment Revisited
September 19, 2013 @ 12:52:50

On the SitePoint PHP blog today David Shirley has a new tutorial looking at continuous deployment with a bit more detail than his previous post.

In an earlier article I talked about what Continuous Deployment was and how it fits into the modern programming process. We took a small swipe at how it works, but some people (okay, one person) felt that I could have gone into more detail and they were right. [...] The essence of Continuous Deployment is that you use automated tools to do a lot of the heavy lifting. This means there may or may not be a bit of a learning curve when you first get started. A number of software elements are brought into play, and if you already know how to use those, great. If you don't, just remember that this is a learning curve, not a barrier.

He's broken down the rest of the tutorial into sections relating to the different pieces needed to effectively set up a continuous deployment (CD) system:

  • Effective use of version control
  • Commitment to automated testing
  • Setup and use of automated build software
0 comments voice your opinion now!
continuous deployment series detail versioncontrol testing build software

Link: http://www.sitepoint.com/continuous-deployment-revisited

NetTuts.com:
Travis-CI What, Why, How
September 19, 2013 @ 11:10:31

If you've ever wanted to put together automated builds for your project but didn't want to have to worry about all the setup and systems involved, Travis-CI might fit your needs. To help get you started NetTuts.com has posted this introduction to the (free) service and its features.

Travis CI makes working in a team for a software project easier with automated builds. These builds are triggered automatically when each developer checks in their code to the repository. In this article, we will go through how we can integrate Travis CI easily with our project, which is hosted on Github. With automation, notification and testing in place, we can focus on our coding and creating, while Travis CI does the hard work of continuous integration!

They focus on its use in a Node-based project, but Travis-CI is language agnostic, so the ideas still apply to PHP-based apps too. They introduce you to the Travis interface and show you how to hook it into your Github account. They also point out another handy feature of Travis - executing on pull requests to see if the results would break anything if merged. Plenty of screenshots are included in the post showing you different states of passing and failing builds. They also include a bit about showing the build status image in your project's README Markdown file.

0 comments voice your opinion now!
travisci continuous integration introduction nodejs

Link: http://net.tutsplus.com/tutorials/tools-and-tips/travis-ci-what-why-how/

Fortrabbit.com:
Integrating Codeship with Fortrabbit
August 29, 2013 @ 10:30:37

On the Fortrabbit blog today they show how to integrate their service with the Codeship.io service, helping make continuous deployment simpler.

We have got a lot of requests concerning continuous integration lately. That's why we've published a new general article in our docs on how to integrate CI in your fortrabbit workflow. Pieter from wercker also just published this great article on how to integrate fortrabbit with wercker. Here is another one from us on how you could something similar combining Codeship with fortrabbit.

They walk you through the full process with a freshly created Fortrabbit application so you can see how to get it set from the start. The article shows you how to set up Codeship with the repository provider and the callback for push notifications. You'll have to set up a ssh key for Codeship to be able to access the repository and a special script that happens on push to trigger the build. There's also a bit at the end about "going multistage" with a different deployment process for each branch.

0 comments voice your opinion now!
codeship fortrabbit continuous deployment tutorial setup configuration

Link: http://blog.fortrabbit.com/integrating-codeship-with-fortrabbit/

PHPMaster.com:
What's Continuous Deployment?
July 11, 2013 @ 13:29:25

On PHPMaster.com today there's a new article introducing you to a concept more and more development groups are moving towards to keep up with the ever-changing needs of their software - continuous deployment.

As part of [the evolution to agile development], we added the deployment phase to the quick turn around cycle. And this is where Continuous Deployment fits in. Essentially the idea behind Continuous Deployment is that functionality is moved to production as soon as it's coded and tested so it can be used (that is, really tested).

He talks about what continuous deployment (CD) is, the parts of the process that help make it possible and some of the advantages/disadvantages of its use. He also briefly looks at how to get started implementing a CD process in your development group. There's no technology recommendations or anything - just a set of three basic concepts to get the ball rolling.

0 comments voice your opinion now!
continuous deployment introduction development process

Link: http://phpmaster.com/whats-continuous-deployment

Samantha Quinones:
Why you should consider Continuous Integration
June 14, 2013 @ 09:39:32

Samantha Quinones has a recent post to her blog about why you should consider continuous integration for your projects - some of the benefits and decisions that come along with it.

Last night at DCPHP, I gave a short "lightning" talk on Continuous Integration and Deployment in the context of PHP applications. I really like the lightning talk format as it forces you to focus on the meat of your topic- there's no time to get distracted by details. As great as that is, though, I wanted to expand a little on the subject and touch on some of the details that I couldn't include in my presentation.

She starts off by talking about what's wrong with a lot of the more traditional build and development practices, noting that "it sucks" because of the processes involved. With the help of continuous integration, some of the process can be automated and make for less human-related errors during a deployment. She talks about some of the things you'll need to do to prepare your codebase and a few things to think about your future setup like:

  • what does a successful build look like?
  • how much code needs to be covered by tests to deploy?
  • should a build be successful if standards are broken or issues found?
0 comments voice your opinion now!
continuous integration integration opinion automation

Link: http://www.tembies.com/2013/06/continuous-integration-deployment-with-php

Luis Atencio:
Notes on Continuous Delivery - Implementing a Testing Strategy
April 25, 2013 @ 11:55:24

Luis Atencio has posted the latest article in his "Continuous Delivery" series today, this time with a focus on implementing a testing strategy. This is the fourth post in the series (part 1, part 2 and part 3).

There are three things in life that are always held to be true: we will die someday; we will pay taxes; and software will have bugs.... LOL [...] A testing strategy is often overlooked in software projects. This should not be too surprising, we want to build applications quickly and release them quickly. However, leaving quality out of the picture or towards the end are terrible mistakes.

He talks some about the different types of testing that revolve around software development - "business facing" and "technology facing." These are each split down even further into things like acceptance, integration and unit testing.

0 comments voice your opinion now!
continuous delivery testing strategy series

Link: http://www.luisatencio.net/2013/04/notes-on-continuous-delivery.html

Luis Atencio:
Notes on Continuous Delivery - Continuous Integration
March 26, 2013 @ 12:20:31

Luis Atencio has posted the third part of his continuous delivery series (parts one and two), this time with a focus on continuous integration as a part of the process.

This is a continuation from my previous post and overall the series on Continuous Delivery. If you haven't been following, that's okay, every topic is self-contained, so read along. The contents of these posts are taken from the book titled "Continuous Delivery" by Humble and Farley (resources below) overlaid with my own professional experience. In this article, we talk a bit more about Continuous Integration (CI) and some practices developers should follow to ensure a smooth environment.

He talks some about what "continuous integration" is and how much it relies on an automation of the process around your delivery of software. He mentions integration of testing (unit/acceptance/integration) and how it can help discover issues early. He includes a list of essential practices that come along with the idea of CI integration including:

  • Don't check in on a broken build
  • Keep a stable build at all times
  • Anticipate being able to revert your changes
  • Using TDD
  • Distributed Version Control

He also recommends using any downtime (like waiting on a build to "go green" again) to take a few minutes away from the code - it can benefit you and your code.

0 comments voice your opinion now!
continuous delivery overview integration build deploy


Luis Atencio:
Notes on Continuous Delivery - Configuration Management
February 26, 2013 @ 11:55:10

Luis Atencio has continued his series on continuous delivery with this second post. It focuses on the first step (and one of the most important) - keeping everything configuration-related in a version control system.

I will be continuing the topic on Continuous Delivery which began in my previous post: Notes on Continuous Integration; this time we will start looking at the first and most important step, Configuration Management. In the words of the authors (resource below): Configuration Management refers to the process by which all artifacts ... and the relationships between them, are stored, retrieved, uniquely identified, and modified.

He sets out four principles that can be used to set this process up in your workflow:

  • Keep everything in version control
  • Manage dependencies
  • Manage software configuration
  • Manage environments

Each point has an explanation and advice on what he's found the best way to implement the functionality. He finishes with a few other pieces of advice including avoiding branching in config repositories and having good communication practices with your ops team.

0 comments voice your opinion now!
continuous delivery overview configuration management



Community Events











Don't see your event here?
Let us know!


symfony2 unittest install introduction release performance composer hhvm podcast database project component application security facebook hack language framework package example

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework