Strider-CD/strider

trigger build when a dependency changes

Open

#114 opened on Jul 17, 2013

View on GitHub
 (14 comments) (1 reaction) (0 assignees)JavaScript (4,587 stars) (454 forks)batch import
feature requesthelp wanted

Description

That would be so cool. In a project I'm working on, a module we depended on w/ semver'd "N.N.x" made a bugfix release that broke our code, and we didn't realize this until days later.

If we could automatically trigger a build any time a dependency issues a new release (that's still within the version requirements we supplied), that would be such a killer feature, especially for node projects.

Contributor guide

Tech stack
javascriptnodejs
Domain
ci cddevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
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
Basic understanding of npmSemver conceptsCI/CD pipeline knowledgeStrider plugin system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate Strider's hook/plugin architecture and how it can integrate with npm's registry or GitHub releases to detect dependency changes. Review existing comments for any previous attempts or design ideas. Consider building a proof of concept plugin that listens for dependency updates and triggers a build accordingly.