Strider-CD/strider

trigger build when a dependency changes

Open

Aperta il 17 lug 2013

Vedi su GitHub
 (14 commenti) (1 reazione) (0 assegnatari)JavaScript (4587 star) (454 fork)batch import
feature requesthelp wanted

Descrizione

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.

Guida contributor

Tech stack
javascriptnodejs
Dominio
ci cddevops
Tipo issue
feature
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
4
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
3-5 days
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
stale
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
mostly clear
Prerequisiti
Basic understanding of npmSemver conceptsCI/CD pipeline knowledgeStrider plugin system
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
20
Direzione di ricerca
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.