Strider-CD/strider

Simplify the job process

Open

#761 创建于 2015年4月20日

在 GitHub 查看
 (5 评论) (0 反应) (0 负责人)JavaScript (4,587 star) (454 fork)batch import
documentationenhancementhelp wanted

描述

Currently there are just too many separate parts, and it's hard to know what's what and where it comes into play.

I'm referring to strider-runner-core, strider-simple-runner, lib/backchannel.js, job-data-monitor.js, job-monitor.js, etc. (who knowns what else there is for the job workflow..).

It would be nice to simplify some of this workflow. Either by refactor or by some clear documentation.

贡献者指南

技术栈
javascriptnodejs
领域
devopsci cdbackend
议题类型
refactor
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Understanding of Strider job workflowFamiliarity with Node.jsExperience with code refactoring
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
35
研究方向
First, read the existing code in the mentioned files: `strider runner core`, `strider simple runner`, `lib/backchannel.js`, `job data monitor.js`, and `job monitor.js`. Understand how each component fits into the job workflow. Review the issue comments for any prior discussion or proposed solutions. Then, propose a simplified architecture or create documentation explaining each module's role and interactions. Consider opening a discussion with the maintainers to align on the scope before starting work.