Continuous Delivery

Continuous Delivery Tutorials

What is Continuous Delivery?

Find and Address Bugs Quicker

Your team can discover and address bugs earlier before they grow into larger problems later with more frequent and comprehensive testing. Continuous delivery lets you more easily perform additional types of tests on your code because the entire process has been automated. Continue reading this article at Amazon

From agile to DevOps to continuous delivery: An evolution in software delivery

In 2001, The Agile Manifesto changed the landscape of software development with the introduction of agile development. Agile methodologies taught developers to break down software development into smaller chunks known as “user stories,” which accelerate feedback loops and align product features with market need. Continue reading this article at TechBeacon


Successfully implementing DevOps in your organization puts you one step closer to Continuous Delivery. Continuous Delivery is the notion that as soon as a feature or feature set has been completed, it can be automatically rolled into production. According to an Amazon presentation from the Velocity conference in 2011, Amazon rolled a new feature out to production every 11 seconds in May of that year. Not every 11 days. Not every 11 hours. Every. 11. Seconds. That is Continuous Delivery at its finest. Continue reading this article at 3 Pillar

Containers, DevOps, Continuous Delivery: Put your X in the box

There are just 14 days to go until 40 of the top brains in DevOps, Continuous Delivery, Containers and Agile come together at Continuous Lifecycle London, and there’s still time for you to grab a ticket. Continue reading this article at The Register

What is Continuous Delivery?

Continuous Delivery also supports two other patterns for progressive exposure beside sequential rings. “Blue/Green deployment” relies on keeping an existing (blue) version live while a new (green) one is deployed. Typically, this uses load balancing to direct increasing amounts of traffic to the green deployment. If monitoring discovers an incident, traffic can be rerouted to the blue deployment still running. “Feature flags” (or “feature toggles”) comprise another technique used for experimentation and “dark launches.” Feature flags turn on features on or off for different end users based on their identity and group membership. Continue reading this article at Microsoft

The Product Managers’ Guide to Continuous Delivery and DevOps

Common traits of organisations who have a so-called DevOps culture are: autonomous poly-skilled teams (Steve, Annie and Joey are all on the same team), high levels of test and release automation (a la continuous delivery) and common goals between the poly-skilled members. Continue reading this article at Mind The Product

DevOps vs continuous delivery

DevOps promotes the idea of the three ways: systems thinking, amplifying feedback loops and developing a culture of continual experimentation and learning. It’s about CALMS: Culture, Automation, Lean, Metrics, Sharing. It’s about improving the visibility, testability and optimisation of making changes. Continue reading this article at Working With Devs

Continuous delivery

The CD book written by Jez Humble and David Farley popularized the term, however since its creation the definition has continued to advance and now has a more developed meaning. Companies today are implementing these continuous delivery principles and best practices. Difference in domains, e.g. medical vs. web, are still significant and affect the implementation and usage. Well-known companies that have this approach include,,[citation needed] Facebook,[citation needed] Google, Paddy Power and Wells Fargo. Continue reading this article at Wikipedia

Continuous everything in DevOps…what is the difference between CI, CD, CD…?

“Continuous” is one word that you would often hear again and again in any discussion around DevOps. Almost everything in DevOps is continuous: be it continuous integration, continuous deployment, continuous delivery, continuous testing and so on. Let’s take a closer look at the idea of continuity and why is it so central to the DevOps practice. Continue reading this article at Accenture

The Relationship Between Dev-Ops And Continuous Delivery: A Conversation With Jez Humble Of ThoughtWorks

When you’re talking about continuous delivery, you can count on Jez Humble, Principal Consultant at ThoughtWorks, having an opinion. After all, he literally wrote the book. I recently had a chance to speak with Jez in preparation for his speech at Forrester’s Application Development & Delivery Forum, September 22-23, in Boston, about the relationship between continuous delivery and dev-ops, an issue Forrester has written about extensively and sometimes with some controversy. Continue reading this article at Forrester

Understanding DevOps – Part 2: Continuous Integration and Continuous Delivery

Some organizations have taken this notion of Continuous Delivery to the extreme. They really do deliver every update made by developers out to users on a regular basis. Flikr is one such example. They
deliver multiple updates a day! While this works great for a website, it is probably not going to be viable for enterprise or mission critical software. In fact, I don’t want my bank to be updating their customer account management software several times a day. Take your time… I want access to my money NOW; I can wait for the latest feature. Continue reading this article at Sanjeev Sharma’s Site

Understanding DevOps – Part 6: Continuous Deployment vs Continuous Delivery

So, what is required is the tested and validated capability to deploy to any environment in your delivery lifecycle – all the way out to production. You may only continuously deploy to an environment before ‘Prod’ – UAT/Pre-prod…, but the environments you do deploy to should be ‘production-like’, so you know with very high confidence, that the final deploy to production will work without issues, when you do really need to deploy to it. Continue reading this article at Sanjeev Sharma’s Site

Why continuous delivery?

It is often assumed that if we want to deploy software more frequently, we must accept lower levels of stability and reliability in our systems. In fact, peer-reviewed research shows that this is not the case—high performance teams consistently deliver services faster and more reliably than their low performing competition. This is true even in highly regulated domains such as financial services and government. This capability provides an incredible competitive advantage for organizations that are willing to invest the effort to pursue it. Continue reading this article at Continuous Delivery

Continuous Delivery is Eating DevOps as Software is Eating the Business

Businesses are increasingly relying on software. The automobile industry is a good example, but by no means the only one. Automotive manufacturers today utilize embedded software in the form of ECUs (electronic control units) to control systems throughout the car. Cars can have up to 10 million lines of code and 125 ECUs or more in them. When automotive manufacturer Tesla discovers an issue with its cars, it delivers the software directly to the owner in the form of a download the owner initiates from within the car. This process saves Tesla millions of dollars – unlike the process that traditional automotive manufacturers use, which requires expensive physical recalls when an engineering or manufacturing issue is discovered. That’s the kind of leap modern software delivery practices – such as continuous delivery – can provide to the business. Continue reading this article at CloudBees

What’s the relationship between DevOps and Continuous Delivery?

Yaniv Yehuda is the Co-Founder and CTO of DBmaestro, an Enterprise Software Development Company focusing on database development and deployment technologies. Yaniv is also the Co-Founder and the head of development for Extreme Technology, an IT service provider for the Israeli market. Yaniv was a captain in Mamram, the Israel Defense Forces computer centers where he served as a software engineering manager. Continue reading this article at IT Pro Portal

What is the difference between continuous integration, continuous delivery and DevOps?

As for DevOps, that’s a whole other ball of wax. People often think DevOps is a role or a tool, but it’s really a culture. You don’t “do” DevOps. Here’s a quote from Mike Kavis that I like quite a bit:

“DevOps is a culture shift or a movement that encourages great communication and collaboration (aka teamwork) to foster building better-quality software more quickly with more reliability.” Continue reading this thread at StackOverflow

Continuous Delivery, DevOps & Jez Humble: It’s All About the Customer

“When a C-level person approves a project and analysts come up with a big list of requirements, these aren’t really requirements – they are guesses, or hypotheses,” Jez said. No one really knows yet if the product will actually address the needs of its target customers, whether internal or external. “That’s where continuous delivery comes in; it makes it more economical for you to run lots and lots of experiments.” Continue reading this article at Puppet

Is Continuous Delivery and DevOps Replacing Agile?

As an ALM Software Developer, Intland Software has remained at the cutting edge of Software Development for over 20 years by constantly evolving our product to take into consideration the latest trends in Development by adding and enhancing features. Here at Intland Software we advocate the Scaled Agile Framework (SAFe) which as the name implies is for Scaling Agile for Enterprise use. SAFe supports both the concepts of both Continuous Delivery and DevOps while codeBeamer ALM provides the software features necessary to implement SAFe at Scale. Continue reading this article at Intland

Continuous delivery

In commercial software, Sales and Marketing teams are used to the twice-per-year training seminars, which they plan their years around. In enterprise development shops, the calendar revolves around pre-planned code freezes, planned vacations to respect those code freezes, and the various audits and checks that are the usual cause of the freezes. What if you turned all of that calendar planning on its head? What if instead of two or four large, disruptive releases, you had much more frequent and smaller releases? Continue reading this article at IBM

Scale DevOps and Continuous Delivery with SAFe

Lean UX is not about pixel perfect designs that navigate well and follow style guides. Lean UX is about hypothesis driven development. And as soon as you say hypothesis, either In the context of Lean Startup at the epic level, or Lean UX, the feature level, it changes the expectations. Continue reading this article at Version One

DevOps and Continuous Delivery: Made for a Cloud World

DevOps, from an operational perspective, represents the next step in IT operations for complex software systems. Over the years, the evolution of Storage Area Networks (SAN) and the advent of virtualization technology have transformed the daily work of operations departments from one of maintaining physical hardware to one where they expect reliability from the infrastructure and can increase the level of differentiated value brought to the organization. Continue reading this article at Code Magazine

Using Kanban for DevOps and Continuous Delivery

We wouldn’t suggest applying DevOps at the user story level. Whatever you define as your MMF (minimum marketable feature) or Epic, or Release (any unit really) should probably be WIP limited, not individual stories. It’s possibly the only sensible easiest way to help map and manage your entire value – stream. Continue reading this article at Digite

Embrace DevOps and Continuous Delivery to Kiss Versioning Goodbye

Think about it: can you remember the last time you experienced a maintenance upgrade with Zappos or Facebook or one of the other modern, web-based retailers? Probably not, because DevOps in general and continuous delivery specifically have been baked into their operations from the beginning. Continue reading this article at 10th Magnitude

Understand and Build a Continuous Delivery Pipeline

Injecting resilience patterns into daily work. Fail early and fail often, as the DevOps saying goes. Simulate disaster by subjecting systems to fatal stresses to learn better how to react to failures. The Handbook cites the Netflix ‘chaos monkey,’ which intentionally kills processes and servers during production hours to force teams to build resilience into their work approach. Continue reading this article at SumoLogic

Continuous Delivery Enables DevOps Reality

On his personal Web site, he maintains “hall-of-shame” lists of organizations that have fallen prey to SQL injection (“totally preventable”) and IoT device hacks (“some call it the Internet of Evil Things”), but when he’s not ranting about software security, he’s actually a pretty nice guy. Continue reading this article at ADT Magazine

Whitepapers and Technical Resource on Continuous Delivery and Continuous Integration

Putting the Continuous Delivery Pieces Together – DeployHub, Ansible, Chef, Puppet, Jenkins and CloudBees

A review of how to build out a complete Continuous Delivery process using the right tools for the job.” Continue reading this post at OpenMake


Continuous testing acts as the key driver for DevOps initiatives to yield desired outcomes. This calls for specialists who understand the nuances of continuous testing through effective end-to-end automation leading to Quality at Speed. Cigniti supports the DevOps needs of organizations by providing solutions that enable automated test orchestration and ensure rapid product development and deployment through an integrated model of continuous integration, continuous testing, and continuous delivery. Continue reading this article at Cigniti


Customization vs Configurations – let’s sort it out. On a surface things seem to stay nice and simple. If you use tools to change system configuration provided by a vendor, you’re doing “configuration”. If you use code to change what system does, you’re customizing. But, what if you’re using APIs provided by a vendor? The difference between customization and configuration aren’t so clear. Continue reading this
article at Beyond PLM


Chef Automate lets you manage changes to both infrastructure and application code, giving your operations and development teams a common platform for developing, testing, and deploying cookbooks, applications, and more. If each of your teams has a different way of deploying software, with their own scripts and hardware, unify the release process with Chef Automate. Continue reading this article at Chef

Continuous delivery & DevOps automation services

Adopting continuous delivery results in an average increase of 21 percent in new software delivered and 19 percent revenue increase directly attributed to the adoption of DevOps methodologies (CA). Automating software delivery benefits an organization in multiple areas. Continue reading this article at RogueWave

IBM unveils BlueMix Continuous Delivery, a central hub for DevOps

With the new service, developers can also exploit toolchain templates to scale toolchains across their enterprise with just a few mouse clicks. Some templates already available include toolchains for building microservices, containers, and cloud-native applications. Continue reading this article at ZDNet

Continuous Delivery, DevOps and Managed Services Providers

But CD does matter for MSPs in a few key ways. First, CD pipelines don’t end with development. They also include production release. For that reason, MSPs who are responsible for helping to manage software in production should be aware of and adapt to CD schedules. They need to prepare for updates that roll into production constantly — not every month or every six months, as they did in the past. Continue reading this article at MSPMentor

Role of Continuous Integration & Continuous Delivery in transforming DevOps

In the autumn of 1968, the first NATO Software Engineering Conference gathered programmers to tackle the “software crisis”. The period that followed not only harnessed the need for effective software solutions but also laid the foundation for the development of a standard lifecycle model. Since then, from the traditional waterfall model to the growing trend of DevOps adoption, the ultimate focus have always been to solve the perennial need for maximizing productivity by optimizing resource allocation. Continue reading this article at Aspire Systems

DevOps Services & Continuous Delivery

Automation of these processes is a top priority, and cloud platforms, such as Microsoft Azure or Amazon Web Services, will be used whenever possible for maximum agility. In addition to the underlying infrastructure, an engagement will include application deployment, smoke test implementation, and integration with any monitoring solution. When complete, your team will be empowered to continue automating and improving this deployment phase. Continue reading this article at Applied Information Sciences


Crucially, the code is only promoted from Dev to Test and Test to Live in the deployment stages. In this way developers gets feedback of their code in each environment. And if there are failures they can understand the errors more easily, where the issue might be and how to get it fixed before the code gets to the production environment. Continue reading this article at Kraftic

What comes first, DevOps or Continuous Delivery?

Such as GIT, Jenkins, SALT, Jira or Trello – they are key to making the practice of Continuous Delivery possible, ensuring that Development QA and IT operations teams are in sync. Continue reading this article at Accesa

Our DevOps Journey: Achieving Continuous Delivery and Improvement

Around this time we discontinued our traditional Project Management Office (PMO) which had centrally controlled all development projects. We decentralized responsibility for delivery to the individual development team managers, embedding Product Owners directly within those teams. This helped further reduce overhead and increased agility. Continue reading this article at SparkPost

DevOps & Continuous Integration

Automated Build Tools: A-A-P, Ant, AnthillPro, Automated BuildStudio, Bamboo, Buildr, Capistrano, CMake, Continuum, CruiseControl, ElectricCommander, FinalBuilder, Gradle, Jenkins, Leiningen, make, Maven, MPW Make, MSBuild, NAnt, nmake, Open Build Service, Perforce Jam, Rake, sbt (Simple Build Tool), SBuild, SCons, Shake, Tweaker, Visual Build, Waf Continue reading this post at QuerySurge

Continuous Delivery and DevOps FAQs

DevOps is another way of working whereby developers and system operators work in harmony with little or no organizational barriers between them towards a common goal. This may not sound too radical however when you consider how mainstream organizations function—especially those within government, corporate, or financial sectors—and take into account the many barriers that are in place between the development and the operational teams, this can be quite a radical shift. Continue reading this article at Packt

DevOps and continuous delivery: How much is hype versus reality?

On the panel alongside QA Financial’s editor, Matthew Crabbe, were Elaine Friedman, managing director of global product planning, analysis and strategic support at BNY Mellon Treasury Services; Lee Fulmer, managing director for the investment bank COO office at UBS; Jay Pickett, director of wire payment and correspondent banking operations at the Bank of Montreal and Jan Wildeboer, EMEA open source evangelist at North Carolina-based Red Hat. Continue reading this article at QA Financial

Practices for DevOps and Continuous Delivery

Another practice that I like to implement on my teams is to develop on production-like environments. Reducing the discrepancy between development and production allow developers to find problems faster. A few examples of discrepancies that I’ve seen create problems: developing on Windows machines and deploying to Linux servers in production; running against different database systems or application servers; having different versions of libraries and dependencies; Continue reading this article at InfoQ

DevOps 101: Continuous Delivery

The action that kicks off this workflow is a commit from a developer on one of the development teams. This kicks off the continuous integration phase. This is usually facilitated by a Continuous Integration server such as Jenkins, Bamboo, TeamCity or a service such as TravisCI, CircleCI, or Codeship. At this point, the CI server will execute a set of tests such as unit tests, syntax tests, and validation. Continue reading this article at Universal Mind

15 DevOps Experts Opinions on Continuous Integration and Continuous Delivery

David Bernstein is the author of Beyond Legacy Code: Nine Practices to Extend the Life (and Value) of Your Software. He says, “I’ve written a lot about CI and CD. It’s one of the nine core practices in my new book. The first principle of the Agile Manifesto is, ‘Our highest priority is to satisfy the customer through the early and continuous delivery of valuable software.’ The practice of Continuous Delivery is the only way I know to achieve this principle and is at the very core of Agile software development.” Continue reading this article at The Next Web

Achieving cloud-native operability with microservices, DevOps, and continuous delivery

Software developers like to make lists of three things and then say, smugly, “Pick any two.” For example, the Project Management triangle is good, fast, cheap (pick any two), and the CAP Theorem offers consistency, availability, and partition tolerance (pick any two). Continue reading this article at OReilly


Microsoft is investing big to help you develop your Azure skillset. We put together three training offers that combine free access to our library of flexible, online courses, discounts on our industry-standard Microsoft Certified Professional exams, and a discount on Linux certification, offered through the Linux Foundation. Continue reading this article at Microsoft

Can DevOps and Continuous Delivery Work with Commercial Off the Shelf Software?

Open COTS applications allow for significant modifications to functionality, data, and/or interfaces. These platform typically have rich SDKs, APIs, and embedded developer utilities that enable users and developer to modify all layers of the applications, namely presentation, business logic, and data. Open COTS applications typically have a large, complex footprint consisting of core services, data and/or GUI customizations, embedded applications, etc. Classic examples of open COTS solutions include ERP/CRM platforms (like SAP or Oracle) or portal platforms like Sharepoint, ServiceNow, or Websphere.
Continue reading this article at EMC

Agile, DevOps, Continuous Delivery

The key factor that differentiates top-performing Agile development teams from their peers is not a matter of technical skill. Data from over 300 Agile teams shows that the best teams excel in soft skills, like learning agility, collaboration, and business engagement. Continue reading this article at CEB

The Differences Between Continuous Integration, Continuous Deployment, and Continuous Delivery

Continuous integration, delivery, and deployment are hot terms in today’s DevOps world, so it’s important to define what they mean and understand their similarities and differences. In general, CI tends to focus on keeping software functional at the development level, while CD tends to focus on the state of the final product. However, depending on the needs of your company and the complexity of your application, you may utilize one or the other (or even both!) for a truly customized pipeline appropriate for your needs. Continue reading this article at Rigor


deliver uploads screenshots of your application, all relevant metadata and required binaries to iTunes Connect. This feature can be used to submit an iOS application to App Store review. Typically, this feature is used when your tests are passed and you have the release version of your app ready. Continue reading this article at Bitbar

5 Elements for Successful Continuous Delivery in a DevOps World

As we know, people are the most important factor for a successful DevOps implementation. A project manager ensures that the team is cross functional (BA, QA, developers, Ops, functional and technical SMEs) and well balanced. The project manager must ensure that Ops professionals think like coders–and coders who understand the need of resilience. They share the common business goal–to deliver business value. Continue reading this article at Project Management

Continuous Integration and Continuous Delivery

You can choose to opt in or out of any of the micro services within fabric8; for example use any git repository hosting or Nexus installation. The Chat integration works with hubot so that it can work with any back end chat service such as IRC, Slack, HipChat, Campfire etc. Continue reading this article at Fabric8

DevOps and Continuous Delivery for Oracle SOA and BPM

This is especially the case for Oracle SOA and BPM projects, which involve integrating multiple systems together. It is a common mistake for all parties to agree on the interfaces between the systems and then go off and code independently, with each party making invalid assumptions about how the other systems will behave. The bigger the batch, the longer these assumptions remain undiscovered, and the greater the number of defects in the batch. A significant amount of the time taken to fix a defect is actually spent trying to isolate the problem and determine the root cause, rather than fixing the problem. Continue reading this article at Rubicon X Red

Why DevOps, Integration, and Continuous Delivery Hold The Key to Enterprise Mobile App Dev

Mobile consumers are demanding more apps than ever before. McKinsey & Company predicts that app-related revenues will reach $70 billion by 2017, with 268 billion downloads. The demand for mobile services of every kind is insatiable. Apps now reign supreme and are the new point of access to Web-based programs such as Facebook, Google Apps, Amazon, Dropbox, and LinkedIn. Consumers want more than daily functional updates to their apps — including user experience and user interfaces — and without interruption to service. Some companies update their apps as many as tens of thousands of times daily, all in real time and without interruption. Continue reading this article at Forbes

What DevOps & Continuous Delivery can do for your business

Many of us rely on apps to organise and manage our personal, social and working lives. We communicate with others through apps, plan and book outings and holidays using apps and manage our business schedules using apps. As this era of digitisation continues to grow, it’s the organisations that can adapt that get ahead of the competition and increase their market share and profits. Continue reading this article at Base 2

What security experts need to know about DevOps and continuous delivery

Secondly, there is an urge to protest against DevOps with arguments regarding “separation of duties”. If you fall into this camp, you need to read the DevOps Audit Defense Toolkit. It will open your eyes to what separation of duties is intended for and how DevOps integrates into environments requiring heavy separation of duties. Continue reading this article at Signal Sciences

Continuous Delivery

Application Performance Management solutions while not traditional CD, are an effective ways to prevent code issues from being released. When they exist in pre-production and production, the performance impact of changes can be compared against existing baselines. Continue reading this article at Exagenica

Acquia Powers Up Continuous Delivery with Acquia Cloud CD

Acquia is the leading provider of cloud-based, digital experience management solutions. Forward-thinking organizations rely on Acquia to transform the way they can engage with customers — in a personal and contextual way, across every device and channel. Acquia provides the agility organizations need to embrace new digital business models and speed innovation and time to market. With Acquia, thousands of customers globally including the BBC, Nasdaq, Stanford University, and the Australian Government are delivering digital experiences with transformational business impact. Continue reading
this article at Acquia

The Evolution from Agile to DevOps to Continuous Delivery

Operations teams, however, are finding themselves struggling to deal with releases on a much more accelerated basis. This has created many software release challenges, as Knight Capital Group discovered when the organization suffered a $440 million dollar loss due to old software that was inadvertently reactivated when a new program was installed. Continue reading this article at

Continuous Delivery, the ObjectStyle Way: Interview with Team Lead & DevOps Aficionado Evgeny Vintik

There are tons of other tools, of course. I would recommend anyone looking for language- and platform-agnostic instruments to try BitBucket’s Pipelines. You don’t even need to set up a server to run it. Continue reading this article at ObjectStyle

Delivering Continuous Delivery, continuously

In order to convince everyone of the value of Continuous Delivery, we rolled out the new release process slowly. We started with lower profile, less risky systems using Google App Engine which made deploying frequently much easier. Once we had this in place, we made sure to make the most of it. We deployed frequently and sought opportunities to provide small features or fixes rapidly. This meant that users became advocates for Continuous Delivery, asking why other software couldn’t be delivered in the same way. Continue reading this article at The Guardian

DevOps success: 4 reasons teamwork comes first

DevOps is quickly becoming increasingly mainstream in enterprises. Why? Because a DevOps culture gives companies a competitive advantage by streamlining processes internally. A DevOps approach allows companies to develop and deploy software more efficiently and effectively, meaning businesses can respond to changing customer needs and competitive pressure faster than before. Continue reading this article at The Enterprisers Project

Do You Need Continuous Delivery and DevOps?

According to James P. Womack and Daniel T. Jones, “Lean Thinking is a business methodology which aims to provide a new way to think about how to organize human activities to deliver more benefits to society and value to individuals while eliminating waste.” In my opinion, Continuous Delivery and DevOps are the application of Lean Thinking to a part of the software development lifecycle. In particularly, the processes that occur from the planning of software development to deployment of the software into production. Continue reading this article at CC Pace

Advantages of DevOps Continuous Delivery Model

This is an objective of any software development firm, isn’t it? High value earlier! It’s an objective of DevOps too. Frequency in high quality releases can be easily achieved with constant communication between Development and Operations. Continue reading this article at MSys

DevOps, Continuous Integration, and Continuous Delivery

In this talk we’ll give you an overview of a platform, called Software Factory, that we develop and use at Red Hat. It is an open source platform that is inspired by the OpenStack’s development’s workflow and embeds, among other tools, Gerrit, Zuul, and Jenkins. The platform can be easily installed on an OpenStack cloud thanks to Heat and can rely on OpenStack to perform CI/CD of your applications. Continue reading this article at 126Kr

7 keys to achieving DevOps & Continuous Delivery with Oracle

After a while, we’ve seen bridges grow by themselves. We’ve also observed that the greater the cohesion between Dev and Ops teams is, the greater the business value of the delivered solutions and capabilities will be. The full benefits of DevOps are realized down the track, when its concepts become Business As Usual (BAU). Continue reading this article at LimePoint

Continuous Delivery: once you’ve mastered it…there is no going back.

That is when DevOps was found. A new, SMART development methodology that changed our perspective on software development forever. Instead of focussing on the functionality of the software, we had to focus on the functionality of the process. Continue reading this article at TMNS

DevOps – Continuous delivery of value

This definition is a collection of steps that will run on each commit of the development team. VSTS allows us to compile a wide variety of technologies, such as MSBuild, Xamarin, Android, Xcode, Grunt, etc. For the handling of dependencies there are tools available such as Nuget or npm. Finally a variety of tools for automating testing, as MSTest, Xamarin Test Cloud, Cloud Load Tests, etc., can be included. In case you need to run specific scripts, utility tools can be used, such as Windows PowerShell or a Shell Script using bash. Usually the last step of a build is a publish that will generate the artifacts that then will be deployed with a Release definition. Continue reading this article at Arkano

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s