Faster and more flexible pipelines with a Directed Acyclic Graph

Re:Faster and more flexible pipelines with a Directed Acycli... by epage on Tuesday May 12, 2020 @01:32PM (#23156854)

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.

[ Parent | on HN ]

Re:Faster and more flexible pipelines with a Directed Acycli... by jayd16 on Tuesday May 12, 2020 @03:13PM (#23158376)

Can't you do something like:

    -Stage1 needs A, B, C
    -D needs Stage1

[ Parent | on HN ]

Re:Faster and more flexible pipelines with a Directed Acycli... by epage on Tuesday May 12, 2020 @03:20PM (#23158460)

Basically 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 :)

[ Parent | on HN ]

Re:Faster and more flexible pipelines with a Directed Acycli... by jayd16 on Tuesday May 12, 2020 @03:22PM (#23158488)

I don't disagree. Just trying to help.

[ Parent | on HN ]