Continuous Delivery - An Example

An example of an idealized, modern software delivery pipeline might look like the following:

 • Plan user stories and manage issues with a project management tool like JIRA.
 • Collaborate on code via GitHub pull requests or a code review tool.
 • Kick off a build in a CI system like Jenkins or Bamboo.
 • Automatically run unit and functional tests with open source testing tools like xUnit and other testing frameworks, and automation tools like Selenium and Appium.
 • Deploy with an IT automation tool like Puppet or Chef, or using a PaaS.
 • Monitor performance and impact on business metrics with systems like New Relic and Mixpanel.

Comments

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros
Read more