展示HN:WatchTurm – 我在工作中使用的开源发布可见性层

1作者: WatchTurm3 个月前原帖
我创建这个工具是为了应对在多仓库、多环境设置中反复出现的问题:要回答“实际在什么地方运行什么?”这个问题,竟然需要检查多个系统,这实在是太困难了。 WatchTurm 是一个开源的发布可见性层。它从 GitHub、Jira 和 CI(例如 TeamCity)等来源聚合元数据,生成环境状态的结构化快照,并在一个统一的控制视图中展示出来。 它并不替代 CI/CD 或管理部署,而是位于自动化之上,纯粹关注可见性: - 每个环境中运行的版本 - 环境之间的差异 - 发布之间的变化 我目前在日常工作中使用它,非常希望能收到技术反馈,特别是来自拥有多环境管道的团队的反馈。 代码库链接:<a href="https://github.com/WatchTurm/WatchTurm-control-room" rel="nofollow">https://github.com/WatchTurm/WatchTurm-control-room</a>
查看原文
I built this to solve a recurring problem in multi-repo, multi-environment setups: it’s surprisingly hard to answer “what is actually running where?” without checking several systems. WatchTurm is an open-source release visibility layer. It aggregates metadata from sources like GitHub, Jira and CI (e.g. TeamCity), generates a structured snapshot of environment state, and surfaces it in a single control view.<p>It doesn’t replace CI&#x2F;CD or manage deployments. It sits above automation and focuses purely on visibility: - what version runs in each environment - how environments differ - what changed between releases<p>I’m currently using it in my own daily work and would really appreciate technical feedback, especially from teams with multi-environment pipelines.<p>repo: <a href="https:&#x2F;&#x2F;github.com&#x2F;WatchTurm&#x2F;WatchTurm-control-room" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;WatchTurm&#x2F;WatchTurm-control-room</a>