Define separate steps in pr.yml

[fekete965]

I thought it would be easier to see which step failed in the future if they are in a separate step.

[KevinVandy]

Not familiar with Github Actions as much as Gitlab or BitBucket, but wouldn't we have to set up a bunch of caches and artifacts between the steps to do this? I think we can already easily look at the console output to see while pipelines fail, so we might leave this alone?

Your work that you've contributed is highly appreciated though. I could be wrong and this might be better.

[KevinVandy]

Actually this pipeline ran your modified pipeline just fine, probably will merge

[fekete965]

Not familiar with Github Actions as much as Gitlab or BitBucket, but wouldn't we have to set up a bunch of caches and artifacts between the steps to do this? I think we can already easily look at the console output to see while pipelines fail, so we might leave this alone?

Your work that you've contributed is highly appreciated though. I could be wrong and this might be better.

Sorry for the late reply! Today's my wife's birthday 🎂 and I was out with her. :D

If you create multiple jobs, then each job will run on a different virtual machine (as far as I know).
If you do that and want to reuse certain data, you need to handle the cache somehow.

If you define steps inside a job, those will be run on the same VM one after another, so cache management is not needed. :)