I'm a self-taught dev focused on websites and Python development.
My friends call me the "Data Genie".
When I get bored, I find tech to read about, write about and build things with.
The downside of using two jobs is that you need extra code to save the build output from the one job and then open it in the second job. Because by default, nothing is persisted across jobs.
You're correct about the lack of persistence across jobs. In the specific example from my post, the deployment step used to do a clean build every time so I opted to go for a separate job which would guarantee that releases wouldn't share any build outputs with the tests.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Here is my recipe for deploying a Node app to GH Pages. Instead of two jobs, I have one job and just have the last step run conditionally
michaelcurrin.github.io/code-cookb...
The downside of using two jobs is that you need extra code to save the build output from the one job and then open it in the second job. Because by default, nothing is persisted across jobs.
You're correct about the lack of persistence across jobs. In the specific example from my post, the deployment step used to do a clean build every time so I opted to go for a separate job which would guarantee that releases wouldn't share any build outputs with the tests.