Hi ,
I have two configurations - One that build and deploys application to QA and another that just deploys to PRODUCTION
The question is - how application that deploys to Production can access artifacts that created during building QA version?
Hi Sergey,
There is currently no general way to give one build access to the workspace (and artifacts) of another.
One option would be to use a Copy action to copy the artifacts to a fixed external folder at the end of the QA build. The Production build would then copy (or link to) the files from the external folder at the start of the first stage. In this case, you would need to make use of Shared Resource locks to ensure there are no concurrency issues.
Another option (and this is what we use), is to add a Production deployment stage to the end of your build configuration, after the QA deployment stage. Set the QA deployment stage to manual promotion (untick the “Always automatically promote to next stage”). The build will then stop at the end of the QA deployment stage, and require manual promotion to move on to the Production stage.
If you need to run the Production deployment stage without running the QA deployment stage at any time you can add a skip condition to the QA deployment stage and control this with a prompted variable or trigger variable.
We have had a plan for some time to add a feature to specify dependencies for each configuration, but this is unfortunately still waiting on our back log for us to schedule time for.