Explore chapters and articles related to this topic
Cloud DevOps
Published in Haishi Bai, Zen of Cloud, 2019
Continuous integration (CI), continuous delivery, and continuous deployment are related terms. Continuous integration is a software development process in which a new build and automated unit tests are automatically triggered whenever a developer checks in new code. This practice enables bugs to be discovered early. In some systems, a code check-in is allowed only when automated tests are passed—this is called gated check-in. Continuous delivery pushes the process further by adding automated integration tests and acceptance tests to ensure the software package remains at a production-ready quality all the time. Finally, continuous deployment automates the last step—deploy to production. With continuous deployment, every code check-in automatically goes through the entire pipeline and ends up in production. Having new versions automatically pushed to production may sound dangerous. However, statistics have shown that most deployment problems are caused by human factors. Eliminating human factors allows more frequent and more reliable deployments, which drastically shortens the customer feedback loop because customers always have access to the latest version.
Role of Open Source, Standards, and Public Clouds in Autonomous Networks
Published in Mazin Gilbert, Artificial Intelligence for Autonomous Networks, 2018
Continuous delivery extends the CI process by preparing and testing the new build for production deployment. This involves pushing the CI-tested build to a staging environment where additional tests (e.g., API, load, and reliability) prior to deployment can be performed. If everything checks out, then the developer manually signs off and the code is ready for deployment to a live production environment. Continuous deployment removes the manual developer sign-off, and the entire release process beginning with code all the way through to production deployment is automated.
Lean Primer for IT Professionals
Published in Michael A. Orzen, Thomas A. Paider, The Lean IT Field Guide, 2017
Michael A. Orzen, Thomas A. Paider
Continuous Delivery (or Continuous Deployment) is all about releasing functional software more frequently and in small chunks. This applies to companies that actually sell software (think Intuit) as well as companies who rely on software to deliver products and services (think Amazon). Continuous delivery (CD) leverages automation, recurrent releases of code, testing at every stage of the process, and a pull-based work flow that permits only successful releases to move to the next stage in the release cycle.
DevOps adoption: Insights from a large European Telco
Published in Cogent Engineering, 2022
António Trigo, João Varajão, Leandro Sousa
Regarding status quo (Q1), it was possible to verify, by direct observation, that some of the DevOps practices, processes, and tools already existed in the company before the DevOps adoption, which was also later confirmed by the interviewees. The company used continuous integration and continuous delivery practices, but not in the form of an automated pipeline. Planning and automated testing processes were also in use. Concerning DevOps tools, the use of a central code repository, a compilation orchestrator, and deploy and monitoring tools were identified. One example is the use of Jenkins orchestrator for automation processes of some compilations and product installation. To sum up, before DevOps, the company already had some of the required practices, processes and tools, but was experiencing significant communication problems with both Devs and Ops teams. There were also opportunities for improvement by adopting new good practices.
Coordinating continuous-time distribution and sales planning of perishable goods with quality grades
Published in International Journal of Production Research, 2018
Wolfgang Albrecht, Martin Steinrücke
The main contributions of the paper include the connection of continuous delivery times (spent on the distribution) with discrete quality grades by the effects on the revenues achievable at the markets. As these effects occur after exceeding specific shelf-life thresholds, an exact coordination of processes at/between the network sites is ensured in order to meet these thresholds so as to realise the maximum profit of the overall system. The optimisation of the distribution structure is captured by enabling any composition of material flow paths possibly directed via warehouses of different SC stages. By introducing a method based on power sets, it becomes possible to coordinate the scheduling of partial and entire material flow paths.
An outlook at Agile methodologies for the independent games developer
Published in International Journal of Computers and Applications, 2021
Renae Aurisch, Mohiuddin Ahmed, Abu Barkat
The hybrid model, Scrumban, adds elements of both methodologies together and creates a method that can mold to the users’ desires. It provides additional optimized workflow to Scrum's time-boxing of events and creates a middle ground of visual and verbal communication. Unlike Kanban, Scrumban utilizes the framework provided by Scrum and gives structure to the flexible properties of Kanban. With Kanban's benefits of continuous delivery and market-driven development, Scrumban is able to use goal setting, capacity management, team empowerment and self-organization to reap the benefits of Scrum's communication and structure focus allowing improved quality, team moral and products.