如何在我的发布流程中添加一些内容？
我负责产品和产品的合并、部署和发布。我工作的公司的服务。我慢慢地从开发转到了这个职位，所以很多内容对我来说都是新的（我猜！）
我们有一个部署过程，但除了告诉利益相关者和员工这些新服务/功能/之外，没有真正的发布程序发布前不久修复了错误。
我听说过有关 ITIL 发布管理、CMDB、版本控制和其他胡言乱语的事情，但它们真的需要吗？还是我最终会被一堆废话压垮。
我想我想问的问题是：我的第一步是什么？我是小题大做了吗？我该如何塑造这个部门？
史蒂夫
I look after the merging, deployment and release of Products & Services in the Company I work for. I've slowly moved to this position from development so a lot of this is new to me (I guess!)
We have a deployment process, but no real Release procedure other than telling stakeholders and members of staff about these new services/features/bug fixes shortly before release.
I've heard things about ITIL Release Management, CMDB, versioning and other mumbo jumbo, but are they actually needed or am I going to end up being weighted down in by a load of crap.
The question I guess I'm trying to ask is: what's my first step? Am I making a mountain out of a molehill? How do I shape this department?
Steve
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为遵循 ITIL 实践或实施 CMDB 不是必需的，而是最佳实践。就您而言，最重要的事情也是第一步是制定或记录有关您所做工作的合理流程。对于文档，您可以使用“程序员友好”的工具，例如 wiki（MediaWiki、TikiWiki），但如果您不记录您的实践，则很难实现持续改进。
如果您已经实施并记录了您的流程，您可以研究与您的部门相关的标准和最佳实践。 ITIL 和 ISO 20000-1 是专注于您提供的服务质量的标准。服务，而不是持续运营。 ITIL 可以为您提供一些有用（但不是必需）的良好实践，例如实施 CDMB。如果您正确实施 CMDB，您的部门将在数据库中拥有您用于提供服务的资产的配置。您将能够存储客户端上的系统配置或您想要的内容。 CMDB 可以将其元素与事件或已知错误相关联，以便支持部门可以为您的客户提供最好的服务。
CMMI 或 CRUM 是您可能感兴趣的其他标准/框架。
关于版本控制，我认为某种版本控制是必须的。 GIT 或 Subversion 是不错的选择。
我认为其他非常有趣的工具是某种持续集成，例如 Jenkins 和一些票务系统，例如 Trac 或 Mantis。
In my opinion following ITIL practices or implementing a CMDB are not necessary but best practices. The most important thing, and first step, in your case, is developing or documented sound processes about what you do. For documentation you can use "programmer friendly" tools like a wiki (MediaWiki, TikiWiki), but if you do not document your practices it is very difficult to implement continual improvement.
If you have already implemented and documented your processes you can study standards and best practices related to your department. ITIL and ISO 20000-1 are standards focused on the quality of services you offer. Services, not ongoing operations. ITIL can provide you with some useful (but not necessary) good practices like implementing a CDMB. If you implement a CMDB correctly your department will have in a database the configuration of the assets you use to provide your services. You will be able to store the configuration of the systems on your clients or what you want. The CMDB can associate its elements with incidents or known errors so the support department could provide the best service to your clients.
CMMI or CRUM are other standards/frameworks that will probably interest you.
About versioning, I think some sort of versioning is a must. GIT or Subversion are good options.
Other tools very interesting in my opinion is some kind of continuous integration, like Jenkins and some ticketing system like Trac or Mantis.