Hi guys,
With Bamboo OnDemand, I want to chain project deployements, each one being triggered when previous one has succeeded, like QA => Stage => Production.
How do I perform that, knowing the only triggers available are on plan build success, not on project deployment success ??
Maybe my question does not make sense, or maybe it looks stupid, so let me describe you more about my project context :
It is a PHP project, so basically, at the beginning what I expected from Bamboo OnDemand is to :
1 - check out the code from one branch (in BitBucket)
2 - do some PHPUnit test on it on the Elastic Image
3 - deploying the code to one environment
and to redo this "3 - steps" for another environement, and maybe another git branch.
Let's say 3 environments is enough for me (testing/QA, Stage, Prod). And of course I want a chain, each one triggering the next, only if it went well (except for the prod I want to be triggeredmanually)
Problem 1.
I cannot run PHPUnit in Elastic Agent because it seems it does not have the mysql driver .... So far for the automated testing in Bamboo OnDemand.
Solution : I can do the testing on the target server, once the code has been "deployed".
So it means my 1-2-3 steps become :
1 - check out the code from one branch
2 - deploying the code to one environment
3 - do some PHPUnit test on it
Problem 2.
I don't have any resulting artifact, since I don't have to "build" (meaning compile/ link etc.) anything, I'm in php world... I just have source files to be "deployed" (=moved) from the repo to the server.
As an unexpected consequence, it means that if I want to use Project Deployments, I have to create a fake and shared artifact, otherwise I can't create any project deployment ! :(
Moreover, to perform the "deployment", I don't want to use any SCP task that actually move all checked out files over the net, it would be way too long.
Solution : my deployment will only consist in remotely asking for a git pull.
Finally, what I have now is :
(1) A build plan whose sole role is to create a dummy file to be shared as an "artifact", just to allow me have Project Deployments.
(2) One project deployement for QA env., which have only one task, the SSH command task, that connects to the QA server and performs remotely :
- git pull from the "develop" branch to the web root (I'm using Bitbucket and a Gitflow workflow here)
- run local phpunit testing against that code
Then, if testing is OK, I want to do the same for a Stage environment. But how to chain/trigger it ?
And eventually I want to do the same for a Production environment, expect this one will be manually triggered (and source code will be pull from Master branch).
Can you help me to organize this ? :)
best regards,
JS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.