mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-12 01:40:10 +08:00
commit
7ff1f4c27f
@ -2,13 +2,13 @@
|
||||
[#]: via: (https://opensource.com/article/21/3/devops-documentation)
|
||||
[#]: author: (Will Kelly https://opensource.com/users/willkelly)
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: translator: (Veryzzj)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
A DevOps guide to documentation
|
||||
======
|
||||
|
||||
Bring your documentation writing into the DevOps lifecycle.
|
||||
![Typewriter with hands][1]
|
||||
|
||||
@ -56,8 +56,6 @@ Often it's developers who shoulder the work of documenting DevOps practices. Eve
|
||||
* Look for ways to be creative with information gathering, such as recording your team meetings and using chat system logs to serve as a foundation for your documentation.
|
||||
* Establish a wiki for publishing your best practices. Use a wiki that lets you maintain an audit trail of edits and updates. Such a platform sets your teams up to update and maintain best practices as they change.
|
||||
|
||||
|
||||
|
||||
It's smart to document dependencies as you build out your CI/CD toolchains. Such an effort pays off when you onboard new team members. It's also a little bit of insurance when a team member forgets something.
|
||||
|
||||
Finally, automation is enticing to DevOps stakeholders and practitioners alike. It's all fun and games until automation breaks. Having documentation for automation run books, admin guides, and other things in place (and up to date) means your staff can get automation working again regardless of when it breaks down.
|
||||
|
Loading…
Reference in New Issue
Block a user