�ݺ�ߣshows by User: mmjan

�ݺ�ߣshows by User: mmjan / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: mmjan / Thu, 25 Jun 2015 09:58:09 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: mmjan Enabling Continuous Delivery For Major Retailer using open source Jenkins /slideshow/continuous-delivery-framework/49824122 jucdeck16x9final-150625095809-lva1-app6892
This presentation Illustrate's the team's achievements and challenges faced whilst implementing a CD framework for major retailer. By using rigorous but simple dev process integrated with Jenkins build pipelines. Pipelines have been carefully architected to orchestrate various build, deployment, testing and release of ecommerce applications. It highlights the following areas that have enabled the team to transition to CD practices: (1) Developer Environment: Implementation of virtual machines (VMs) for developers so they have all the required tools and applications for executing builds and tests. (2) Continuous Integration: How changes pushed from a VM were continuously built, tested, deployed and released. (3) Continuous Release: How the Jenkins Build Pipeline View was used to orchestrate release processes. (4) Continuous Deployment: How the Jenkins Build Pipeline View was used to orchestrate the deployments to various environments, from CI through to production. (5) Automated Testing: How a testing framework was integrated as a key checkpoint for promoting releases. (6) Environment Configuration: How the environment configuration was decoupled so that the release is environment-agnostic and separately deploys environment configurations. (7) Database Deployment: How the database and data changes were incrementally deployed as part of a Jenkins pipeline. (8) Production Deployment: How the various deployment techniques were addressed (full outage, partial outage, no outage) using Jenkins pipelines. (9) Reporting: How the Build Monitor plugin was used to report various build, deployment, testing and release statuses. (10) Future Activities (cloud-based deployments)]]>
This presentation Illustrate's the team's achievements and challenges faced whilst implementing a CD framework for major retailer. By using rigorous but simple dev process integrated with Jenkins build pipelines. Pipelines have been carefully architected to orchestrate various build, deployment, testing and release of ecommerce applications. It highlights the following areas that have enabled the team to transition to CD practices: (1) Developer Environment: Implementation of virtual machines (VMs) for developers so they have all the required tools and applications for executing builds and tests. (2) Continuous Integration: How changes pushed from a VM were continuously built, tested, deployed and released. (3) Continuous Release: How the Jenkins Build Pipeline View was used to orchestrate release processes. (4) Continuous Deployment: How the Jenkins Build Pipeline View was used to orchestrate the deployments to various environments, from CI through to production. (5) Automated Testing: How a testing framework was integrated as a key checkpoint for promoting releases. (6) Environment Configuration: How the environment configuration was decoupled so that the release is environment-agnostic and separately deploys environment configurations. (7) Database Deployment: How the database and data changes were incrementally deployed as part of a Jenkins pipeline. (8) Production Deployment: How the various deployment techniques were addressed (full outage, partial outage, no outage) using Jenkins pipelines. (9) Reporting: How the Build Monitor plugin was used to report various build, deployment, testing and release statuses. (10) Future Activities (cloud-based deployments)]]> Thu, 25 Jun 2015 09:58:09 GMT /slideshow/continuous-delivery-framework/49824122 mmjan@slideshare.net(mmjan) Enabling Continuous Delivery For Major Retailer using open source Jenkins mmjan This presentation Illustrate's the team's achievements and challenges faced whilst implementing a CD framework for major retailer. By using rigorous but simple dev process integrated with Jenkins build pipelines. Pipelines have been carefully architected to orchestrate various build, deployment, testing and release of ecommerce applications. It highlights the following areas that have enabled the team to transition to CD practices: (1) Developer Environment: Implementation of virtual machines (VMs) for developers so they have all the required tools and applications for executing builds and tests. (2) Continuous Integration: How changes pushed from a VM were continuously built, tested, deployed and released. (3) Continuous Release: How the Jenkins Build Pipeline View was used to orchestrate release processes. (4) Continuous Deployment: How the Jenkins Build Pipeline View was used to orchestrate the deployments to various environments, from CI through to production. (5) Automated Testing: How a testing framework was integrated as a key checkpoint for promoting releases. (6) Environment Configuration: How the environment configuration was decoupled so that the release is environment-agnostic and separately deploys environment configurations. (7) Database Deployment: How the database and data changes were incrementally deployed as part of a Jenkins pipeline. (8) Production Deployment: How the various deployment techniques were addressed (full outage, partial outage, no outage) using Jenkins pipelines. (9) Reporting: How the Build Monitor plugin was used to report various build, deployment, testing and release statuses. (10) Future Activities (cloud-based deployments) <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/jucdeck16x9final-150625095809-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> This presentation Illustrate's the team's achievements and challenges faced whilst implementing a CD framework for major retailer. By using rigorous but simple dev process integrated with Jenkins build pipelines. Pipelines have been carefully architected to orchestrate various build, deployment, testing and release of ecommerce applications. It highlights the following areas that have enabled the team to transition to CD practices: (1) Developer Environment: Implementation of virtual machines (VMs) for developers so they have all the required tools and applications for executing builds and tests. (2) Continuous Integration: How changes pushed from a VM were continuously built, tested, deployed and released. (3) Continuous Release: How the Jenkins Build Pipeline View was used to orchestrate release processes. (4) Continuous Deployment: How the Jenkins Build Pipeline View was used to orchestrate the deployments to various environments, from CI through to production. (5) Automated Testing: How a testing framework was integrated as a key checkpoint for promoting releases. (6) Environment Configuration: How the environment configuration was decoupled so that the release is environment-agnostic and separately deploys environment configurations. (7) Database Deployment: How the database and data changes were incrementally deployed as part of a Jenkins pipeline. (8) Production Deployment: How the various deployment techniques were addressed (full outage, partial outage, no outage) using Jenkins pipelines. (9) Reporting: How the Build Monitor plugin was used to report various build, deployment, testing and release statuses. (10) Future Activities (cloud-based deployments)

Enabling Continuous Delivery For Major Retailer using open source Jenkins from Masood Jan

]]> 1038 1 https://cdn.slidesharecdn.com/ss_thumbnails/jucdeck16x9final-150625095809-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://cdn.slidesharecdn.com/profile-photo-mmjan-48x48.jpg?cb=1642969357 With over a decade of experience, I am a freelance ATG and Agile consultant. Expertise in enabling continuous delivery in various top retailer in UK. I am a strong communicator, excellent team player and years of mentoring skill allowing me to work closely with business and engineering team to drive out business valuable solutions. I am a hardcore agile practitioner, with expertise in TDD, BDD, Test Automation, build and deployment automation, Database automation and expert in continuos Integration. A SUN certified Java professional, talented and accomplished Team Leader with extensive server and web based development background.  Provided direct line management of the team and its p... www.mazataz.com