Civil Rights
Movements, leaders, victories and the continuing fight for equality.
q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
What's New!
Explore the people, places, events, achievements, struggles and stories that shaped our journey.
Movements, leaders, victories and the continuing fight for equality.
Innovation, patents, science, technology and world-changing contributions.
Pioneers, champions, Negro Leagues, records, activism and excellence.
Meet the people whose lives, choices and achievements shaped the journey.
Black towns, communities, institutions and places where history happened.
Moments that changed communities, movements, institutions and the nation.
Mansa Musa was the ruler of the Mali Empire in West Africa. Details recorded here should be sourced; unknown information is left blank.
MORE →Reflects the personal views, recollections, and perspective of the author, Mike Davis.
This is a personal recollection on the Move fire on May 13, 1985
| Part of a series on |
| Software development |
|---|
Continuous delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time.[1][2] It aims at building, testing, and releasing software with greater speed and frequency. The approach helps reduce the cost, time,[3] and risk of delivering changes by allowing for more incremental updates to applications in production. A straightforward and repeatable deployment process is important for continuous delivery.
According to Neal Ford, continuous delivery adopts "Bring the pain forward," tackling tough tasks early, fostering automation and swift issue detection.[4]
Continuous delivery treats the commonplace notion of a deployment pipeline[5] as a lean Poka-Yoke:[6] a set of validations through which a piece of software must pass on its way to release. Code is compiled if necessary and then packaged by a build server every time a change is committed to a source control repository, then tested by a number of different techniques (possibly including manual testing) before it can be marked as releasable.
Developers used to a long cycle time may need to change their mindset when working in a CD environment. Any code commit may be released to customers at any point. Patterns such as feature toggles can be very useful for committing code early which is not yet ready for use by end users.[7] Using NoSQL can eliminate the step of data migrations and schema changes, often manual steps or exceptions to a continuous delivery workflow.[8] Other useful techniques for developing code in isolation such as code branching are not obsolete in a CD world, but must be adapted to fit the principles of CD - for example, running multiple long-lived code branches can prove impractical, as a releasable artifact must be built early in the CD process from a single code branch if it is to pass through all phases of the pipeline.[clarification needed]
Continuous delivery is enabled through the deployment pipeline. The purpose of the deployment pipeline has three components: visibility, feedback, and continually deploy.[9]
According to Yan Cui, when it comes to serverless environments, ephemeral resources should be kept together and have their own deployment pipeline to achieve a high cohesion. However, shared resources that have a long spin-up time and landing zone should have their own separate repository, deployment pipeline and stack.[10]
Continuous delivery takes automation from source control all the way through production. There are various tools that help accomplish all or part of this process.[11] These tools are part of the deployment pipeline which includes continuous delivery. The types of tools that execute various parts of the process include: continuous integration, application release automation, build automation, application lifecycle management.[12]
To practice continuous delivery effectively, software applications have to meet a set of architecturally significant requirements (ASRs) such as deployability, modifiability, and testability.[13] These ASRs require a high priority and cannot be traded off lightly.
Microservices are often used when architecting for continuous delivery.[14] The use of Microservices can increase a software system's deployability and modifiability. The observed deployability improvements include: deployment independence, shorter deployment time, simpler deployment procedures, and zero downtime deployment. The observed modifiability improvements include: shorter cycle time for small incremental functional changes, easier technology selection changes, incremental quality attribute changes, and easier language and library upgrades.[14]
The original Continuous delivery book written by Jez Humble and David Farley (2010) 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. The difference in domains, e.g. medical vs. web, is still significant and affects the implementation and usage.[15] Well-known companies that have this approach include Yahoo!,[16] Amazon,[17] Facebook,[18] Google,[19] Paddy Power[1] and Wells Fargo.[20]
Several benefits of continuous delivery have been reported.[1][15]
Obstacles have also been investigated.[15]
Eight further adoption challenges were raised and elaborated on by Chen.[21] These challenges are in the areas of organizational structure, processes, tools, infrastructure, legacy systems, architecting for continuous delivery, continuous testing of non-functional requirements, and test execution optimization.
 | This section contains instructions or advice. (January 2022) |
Several strategies to overcome continuous delivery adoption challenges have been reported.[21]
| Strategy | Description |
|---|---|
| Selling CD as a painkiller | Identify each stakeholder's pain points that CD can solve, and sell CD as a painkiller to that stakeholder. This strategy helps to achieve buy-in from the wide range of stakeholders that a CD implementation requires. |
| Dedicated team with multi-disciplinary members | Without a dedicated team, it can be hard to progress because employees are often assigned to work on other value streams. A multi-disciplinary team not only provides the wide range of skills required for CD implementation but also smooths the communication with related teams. |
| Continuous delivery of continuous delivery | Organize the implementation of CD in a way that delivers value to the company as early as possible, onboarding more projects gradually, in small increments and eventually rolling out CD across the whole organization. This strategy helps justify the investment required by making concrete benefits visible along the way. Visible benefits, in turn, help to achieve the sustained company support and investment required to survive the long and tough journey to CD. |
| Starting with easy but important applications | When selecting the first few applications to migrate to CD, choose the ones that are easy to migrate but that are important to the business. Being easy to migrate helps to demonstrate the benefits of CD quickly, which can prevent the implementation initiative from being killed. Being important to the business helps to secure the required resources, demonstrates clear and unarguable value, and raises the visibility of CD in the organization. |
| Visual CD pipeline skeleton | Give a team a visual CD pipeline skeleton that has the full CD pipeline view but with empty stages for those they cannot implement yet. This helps to build up a CD mindset and maintain the momentum for CD adoption. The pipeline skeleton is especially useful when the team's migration to CD requires a large effort and mindset changes over a long period of time. |
| Expert drop | Assign a CD expert to join tough projects as a senior member of the development team. Having the expert on the team helps to build the motivation and momentum to move to CD from inside the team. It also helps to maintain momentum when the migration requires a large effort and a long period of time. |
The following practices can enhance productivity of pipelines, especially in systems hosted in the cloud:[22][23][24]
DevOps is a software engineering approach that centers around cultural change, specifically the collaboration of the various teams involved in software delivery (developers, operations, quality assurance, management, etc.), as well as automating the processes in software delivery.[25][26][27]
Continuous deployment is a software engineering approach which uses automated software deployments.[21] In it, software is produced in short cycles but through automated software deployments even to production rather than requiring a "click of a button" for that last step.[1]: 52 Therefore, continuous deployment can be considered a more sophisticated form of automation.[28] Academic literature differentiates between continuous delivery and continuous deployment according to deployment method; manual vs. automated.[2][29]
Continuous deployment is the natural outcome of continuous delivery done well. Eventually, the manual approval delivers little or no value and is merely slowly things down. At that point, it is done away with and continuous delivery becomes continuous deployment.
Source: Wikipedia. Article content is retrieved live through the MediaWiki API.
Continuous delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time. It aims at building, testing, and releasing software with greater speed and frequency. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production. A straightforward and repeatable deployment process is important for continuous delivery.
GoCD is an open-source tool which is used in software development to help teams and organizations automate the continuous delivery (CD) of software. It supports automating the entire build-test-release process from code check-in to deployment. It helps to keep producing valuable software in short cycles and ensure that the software can be reliably released at any time. It supports several version control tools including Git, Mercurial, Subversion, Perforce and TFVC (a la TFS). Other version control software can be supported by installing additional plugins. GoCD is released under the Apache 2 License.
Continuous deployment (CD) is a software engineering approach in which software functionalities are delivered frequently and through automated deployments. Continuous deployment contrasts with continuous delivery (also abbreviated CD), a similar approach in which software functionalities are also frequently delivered and deemed to be potentially capable of being deployed, but are actually not deployed. As such, continuous deployment can be viewed as a more complete form of automation than continuous delivery. Continuous deployment has been adopted by software companies such as Meta, Microsoft, Atlassian, IBM, Adobe, and Tesla.
Content marketing is a form of marketing focused on creating, publishing, and distributing content for a targeted audience online. It is often used to achieve the following business goals: attract attention and generate leads, expand their customer base, generate or increase online sales, increase brand awareness or credibility, and engage a community of online users. Content marketing attracts new customers by creating and sharing valuable free content as well as by helping companies create sustainable brand loyalty, providing valuable information to consumers, and creating a willingness to purchase products from the company in the future. Content marketing starts with identifying the customer's needs. After that, the information can be presented in a variety of long form and short form formats, including news, video, white papers, e-books, infographics, email newsletters, case studies, podcasts, how-to guides, question and answer articles, photos, blogs, etc. Examples of short form content include short blog posts and social media posts. Content marketing requires continuous delivery of large amounts of content, preferably within a content marketing strategy.
Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.
MORE →Shirley Chisholm, elected in 1968.
