Strider-CD/strider

Simplify the job process

Open

#761 opened on Apr 20, 2015

View on GitHub
 (5 comments) (0 reactions) (0 assignees)JavaScript (4,587 stars) (454 forks)batch import
documentationenhancementhelp wanted

Description

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.

Contributor guide

Tech stack
javascriptnodejs
Domain
devopsci cdbackend
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of Strider job workflowFamiliarity with Node.jsExperience with code refactoring
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
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.