@BanzaiMan, thank you for the confirmation.
The reason I’m having them separately is to provide better control over execution time. Also depending on the case, I’d like to run them in different groups: only (1) or (2), (1) and (2), all of them. Let me know if you see any problems with this.
I raised the question because after migrating from Travis shared caches to workspaces I accidentally broke the analytics on the Scan stage I guess the reason is clear know. Is it possible to update the workspace with the changes made on stage Test?
So far I tried the trick with two workspaces:
- stage: Build
script: # compiles sources
- stage: Test
script: # compiles tests, runs them and generates coverage reports
- stage: Scan
script: # does analysis and collects other metrics
And looks like it should be working, but now for each stage, I have two jobs:
(1) a new one which uses either
(2) the old one which uses the outdated
Is that expected? How can I drop the
Note: I triggered the pipeline manually using the “Trigger a custom build (Beta)” feature, could it be the reason?