Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Strong Practices for Rails Applications Continuous Delivery by Nathan Smith & Robb Kidd High-velocity organizations deliver change to their customers quickly in a repeatable and predictable way. This talk will explore some pre-requisites and best practices that will help your team move to safe, continuous delivery of your Rails applications. We will demonstrate the path from code commit, to packaged application, to an updated production environment. All of the necessary steps along the way will be fully automated using Chef Delivery. You will leave with some new ideas, practices, and techniques your team can adopt, continuously delivering value to your customers. Help us caption & translate this video! http://amara.org/v/J37W/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video titled "Strong Practices for Rails Applications Continuous Delivery" by Nathan Smith and Robb Kidd explores essential practices for implementing continuous delivery within Ruby on Rails applications using Chef Delivery. Presented at RailsConf 2016, the talk emphasizes the importance of high-velocity organizations that deliver rapid and reliable updates to their customers. The speakers underscore the necessity of automation and the adoption of DevOps principles to enhance quality while minimizing the time between code commitment and production deployment. Key points discussed in the presentation include: - **DevOps Philosophy**: Defined as a cultural movement that fosters collaboration across teams and emphasizes building and operating high-velocity organizations. - **Engineering Quality vs. Speed**: The balance between achieving high quality and compliance while maintaining a quick innovation rate. The goal is to minimize manual processes that hinder progress. - **Automation of Processes**: Emphasizing the importance of automating workflows to boost efficiency and reduce manual intervention, thereby enhancing the team's capacity to deploy more frequently. - **Continuous Delivery Practices**: Implementing smaller batches of changes as a means to safely deploy applications, assuring customers receive frequent updates without waiting for substantial releases. - **Use of Tools**: The selection of tools like Git for version control, along with Chef Delivery, facilitates a streamlined deployment pipeline, ensuring code quality and rapid iterations through continuous integration practices. - **Testing and Quality Assurance**: The significance of rigorous testing (including unit tests and security checks) to uphold high standards throughout the development process. Tools like RSpec and Brakeman are noted for their roles in testing and auditing. - **Demonstration of Chef Delivery**: Presenting a workflow that illustrates the stages of transforming code changes into production, with a focus on verification, build, security checks, and publishing release artifacts. - **Human Intervention**: The necessity of manual gates within the process, ensuring human inputs help maintain quality and oversight during deliveries. - **Cultural Impact**: The presentation emphasizes that a positive workforce culture leads to better products and outcomes. In conclusion, the speakers advocate for a culture of continuous improvement that embraces failure as a learning opportunity, encourages diversity, and values collaborative efforts among teams. By adopting strong continuous delivery practices, organizations can enhance product quality, maintain compliance, and deliver value to customers efficiently.
Suggest modifications
Cancel
