DEV Community

Discussion on: How to set up a dynamic CI/CD pipeline with Github Actions

Collapse
 
layzee profile image
Lars Gyrup Brink Nielsen This is Learning

Hey @timdeschryver , Awesome article!

How come you're not splitting the steps into separate jobs to parallelize the work?

Collapse
 
timdeschryver profile image
Tim Deschryver This is Learning

The steps are relatively small and fast. I haven't tried it, but I think it won't make much of a difference. It would also make the workflow more complex because it has to share outputs between multiple jobs, I think....

Collapse
 
layzee profile image
Lars Gyrup Brink Nielsen This is Learning

I think it mostly depends on the number of tests and the size of the code base.

You would need to share a build artifact between a build and a deploy job. You could set a condition on the deploy job. Alternatively have build and deploy in the same job but set a condition on the deploy step.

Thread Thread
 
timdeschryver profile image
Tim Deschryver This is Learning

That's also how I think about it 😃
For my OSS projects I feel like it would be an overkill