4 ms·
My problems with this feature: - You can't have a DAG of stages. Sometimes, especially with a monorepo which this touts, the maintenance of the "needs" become
by epage 6y ago
My problems with this feature:
- You can't have a DAG of stages. Sometimes, especially with a monorepo which this touts, the maintenance of the "needs" becomes burdensome and you want to just block on a stage rather than explicitly named jobs
- The visualization of this is subpar.
So far my favorite implementation of this feature is Azure Pipelines. No idea if its coped into Github Actions yet or not (haven't switched over). I hate that is the case because of my underlying caution about Microsoft after the 90s and early 2000s though supposedly they are better now.
- jayd16 6y agoCan't you do something like: -Stage1 needs A, B, C -D needs Stage1
- epage 6y agoBasically faking a stage by making a job? That helps but the "definition" of a stage is still far away from the job definition when you have enough of them and people won't know to update this when they copy/paste a job definition for adding a new test. Plus, visualization is still terrible :)
- jayd16 6y agoI don't disagree. Just trying to help.