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.
Simplify the job process · Strider-CD/strider#761 | Good First Issue