I've had a ball this week getting deployment plans in place for a number of projects (all very simple and very similar) and I have some generic questions.
When creating a deployment project the first deployment (to DEV) downloads the artifact and then I have steps that extract then copy the files (deploy) to the dev server. The deployable artifacts are not environment specific. All config files are excluded and no compile occurs during the build so there are no additional factors on that end (these are cold fusion projects)
Right now I'm downloading, extracting and copying in each environment deployment.
It seems risky but plausible that I COULD exclude the download and extraction steps for all future deployments of this same build since it is stored in a separate "deployment" project directory on the bamboo host during the dev deployment. Thus reusing the artifacts and just copying to subsequent environments in QA and PROD deployments.
There aren't any separate environment specific "folders" created in the bamboo deployment workspace are there? (so that the cwd is the same no matter what environment deployment is being run)? (Or is a new deployment workspace created for each subsequent environment?)
I think the down side is the risk that something could change in the deployment project between the time of the dev deployment and the time of the QA / PROD deployment altering the artifacts that I'm deploying to the advanced envs. (We have very restricted access to the bamboo host so the odds of anything occurring, by a force outside of bamboo itself, is limited).
Can anyone provide any thoughts on whether this is a real risk or not? Unexpected cleanup processes might run?
Thanks in advance,
GJ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.