Home » Tag Archives: Continuous Delivery (page 2)

Tag Archives: Continuous Delivery

Continuous Delivery: CI Tools Setup

devops-logo

This is the second article in the “Continuous Delivery” series. We’ll continue where we left in Introduction to concepts and tools. The goal of this article is to set up a Jenkins server locally through automated and repeatable process with all the artifacts stored in the GIT repository. This will require tools like VirtualBox and Vagrant. It will also require ...

Read More »

Continuous Delivery: Introduction to concepts and tools

software-development-2-logo

This is the first article in a “Continuous Delivery” series. We’ll start out journey with brief explanation of Continuous Delivery. After short exploration of some of the tools used today, we’ll move towards the flow (from setting up brand new environment and getting the code from the repository to the creation of fully tested and verified distribution). Each section will ...

Read More »

Trigger Continuous Delivery every GitHub commit

git-logo

Crucial piece of puzzle when developing web application is Continuous Delivery. Testers or users can by early access to alpha version contribute to development process. Design,  requirements, architecture or performance problems can be catched much sooner. I am going to show how to set up this process with usage of Maven and Jenkins. Target environment is hosted on Tomcat7. Source ...

Read More »

Continuous Delivery for Heroku With Jenkins

heroku-logo

A continuous delivery pipeline that leverages Jenkins and targets Heroku is fairly simple to set up, provided you install the Jenkins Git plugin. With this pipeline, changes to a specific Git branch will result in a Heroku deployment. For this deployment process to work nicely, you should use at least two Git branches, as you’ll want to have one branch ...

Read More »

Continuous Delivery Using Cloud Development Tools

devops-logo

Cloud based online development tooling is continuing to improve, removing barriers to entry with regards to building software as part of a team. We can now get full development environments and most of our build, test, and deployment processes up and running in the cloud using various software as a service and infrastructure as a service offerings. These services are ...

Read More »

Continuous Delivery – Part 6 – Backward & Forward Compatibility

software-development-2-logo

Previous Chapter: Startup – Self Test One very important mind set developers will have to adopt and practice is backward and forward compatibility. Most production system do not consist on just one server, but a cluster of servers. When deploying new piece of code, you do not deploy it to all the servers at once because part of Continuous deployment ...

Read More »

Continuous Delivery – Part 5 – Startup – Self Test

software-development-2-logo

Previous Chapter: A/B Testing So far we discussed Feature Toggle and A/B testing. These two methods enable safe guards that your code does not harm your system. Feature toggles enable to gradually use new features and gradually expose it to users, while monitoring that the system behaves as expected. A/B testing on the other hand let you test how your ...

Read More »

Continuous Delivery – Part 4 – A/B Testing

software-development-2-logo

Previous chapter: Continuous Delivery – Part 3 – Feature Toggles From Wikipedia: In web development and marketing, as well as in more traditional forms of advertising, A/B testing or split testing is an experimental approach to web design (especially user experience design), which aims to identify changes to web pages that increase or maximize an outcome of interest (e.g., click-through ...

Read More »

Continuous Delivery – Part 3 – Feature Toggles

software-development-2-logo

Previous chapter: The Road To Continuous Delivery – Part 2 – Visibility One of the key elements in Continuous Delivery is the fact that you stop working with feature branches in your VCS repository; everybody works on the MASTER branch. During our transition to Continuous Deployment we switched from SVN to Git, which handles code merges much better, and has ...

Read More »

The Road To Continuous Delivery – Part 2 – Visibility

software-development-2-logo

Previous chapter: The road to continuous delivery – Part 1 Production visibility A key point for a successful continuous delivery is to make the production matrix available to the developers. At the heart of continuous delivery methodology is to empower the developer and make the developers responsible for deployment and successful operations of the production environment. In order for the ...

Read More »
Do you want to know how to develop your skillset and become a ...

Subscribe to our newsletter to start Rocking right now!

To get you started we give you our best selling eBooks for FREE!
Get ready to Rock!
To download the books, please verify your email address by following the instructions found on the email we just sent you.

THANK YOU!

Close