TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Limiting breakage with a software deployment checklist

98 点作者 plinkplonk大约 7 年前

7 条评论

pnevares大约 7 年前
The blog post refers to &quot;RCA&quot; three times and &quot;RSA&quot; once, and doesn&#x27;t seem to define either acronym after reading it once.<p>Also this?<p>&gt; And once you fail a build, then every team member in your team has to do deployments and go through the deployment checklist.<p>Sounds like there&#x27;s a piece of context missing from the section before it. You have to do the checklist to deploy, and if you fail once, then every member of your team has to do the checklist as well?
评论 #17009975 未加载
评论 #17010057 未加载
iandanforth大约 7 年前
This is a good place to start but you also need to commit to automating these steps. Copying and pasting URLs is a waste of time, rollbacks should be automatic, contributor lists should be auto-generated etc. Since it takes time to automate each new thing a checklist is still a good idea, but you have to recognize the danger of engineers subverting&#x2F;rejecting the process if you let the list grow much at all.
评论 #17010404 未加载
Annatar大约 7 年前
&quot;We don’t restrict a deployment trigger to specific people. As soon as you are done, go ahead.&quot;<p>So they have no change management process in place and are basically hacking on it &#x27;till it works. Very professional.<p>Does not look like they ever heard of the capability maturity model, either.
评论 #17011722 未加载
评论 #17011542 未加载
评论 #17013203 未加载
protomyth大约 7 年前
On the subject of database indexes, know when you should deploy the indexes. This comes up when adding tables that get populated during deploy. Sometimes, depending on your database, its a really bad move to add the index to the empty table. Its an interesting problem because it might be time critical if you are doing enterprise deploys where you are taking down the whole system for the duration. Probably a less common circumstance these days. Also, getting rid of temporary code needed only for the conversion is a super good thing to remember.
brockers大约 7 年前
I know Dev shops don&#x27;t like processes and forms, but that &quot;checklist&quot; is exactly that. It simply shows that processes and procedures are tools that are useful if that use can be limited.
评论 #17013188 未加载
runlevel1大约 7 年前
We do something similar for changes that are risky, complicated, or manual:<p><a href="https:&#x2F;&#x2F;sendgrid.com&#x2F;blog&#x2F;change-management-keep-it-simple-stupid&#x2F;" rel="nofollow">https:&#x2F;&#x2F;sendgrid.com&#x2F;blog&#x2F;change-management-keep-it-simple-s...</a><p>Doing it formally for every deployment seems like it would kill productivity.
评论 #17010294 未加载
trollopTheJope大约 7 年前
what an unfortunate metaphor
评论 #17009632 未加载