In my scenario, I have two parts for a configuration:
In the build step, an approx ~60GB build will be generated.
The deploy step will then upload these artifacts to a windows file share.
With the concept being to have the deploy step free up the agent whilst a file transfer occurs to network storage. However the archive artifacts on Build is taking a very long time. So any benefit is pretty much lost in having them as separate jobs.
I can forsee the following solutions:
- Remove the artifacts feature from this job, add a build step directly to do the SMB upload in Build.
- The deploy configuration can read direct from the workspace of the dependency Build configuration. (I've not seen this as any variable for the path). This also requires locking the original workspace in some way (So another job can't come along and taint the assets)
- The configuration of the artifacts on Build needs to be improved. Perhaps I'm using something super slow?
- It's a resource problem, there's a blocker within my hardware resources.