DEV Community

Discussion on: Tips and Tricks for GitHub Actions

Collapse
 
msfjarvis profile image
Harsh Shandilya

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.