I have a scenario where we have a task to run smoke tests after the deployment is successful. We would like to know if the deployment failed or if the smoke tests task failed. So, would prefer to receive email notification from bamboo saying deployment is successful and smoke tests task is starting.
Can we accomplish this?
You might want to create a separate build for the smoke tests and add it is a child build of the original deployment build.
That way, you can configure separate notifications for the builds. Also, the smoke tests won't be triggered if the deployment failed. Would that help?
Thanks for the reply. But the way we have it set up is that we have a build plan which generates the artifacts and we have a deployment plan set up which is tied to that build plan. once we have a successful build, the deployment is triggered. I dont see an option to set up dependencies for a deployment plan like we have it for build plans. Am i clear? If not i can try to explain it in more detail. Let me know. Thanks!
Yeah, that's a bummer. You can work around by defining a new environment in the same deployment project that just does the smoke tests. And it can have a trigger to start after the successful deployment of the actual deploy.
It is not pretty as environments are meant for deploys not tests but it is a workaround.
Another option is to use a script task in the deployment to trigger the test plan using the REST API.
Yeah, that's a bummer. You can work around by defining a new environment in the same deployment project that just does the smoke tests. And it can have a trigger to start after the successful deployment of the actual deploy. .>> I just checked and there is no trigger based off a successful deployment .. but there are triggers based of off successful builds ...
Do you have an example script using REST API? I am fairly new to this approach and would like to customize based of your sample.
But thank you so much. You have been extremely helpful!!
I just checked and there is no trigger based off a successful deployment
Did you check the trigger in a deployment env? I was talking about adding a new env and then add a trigger on it to start the env tasks as soon as the actual deploy is done.
Env1: DEV DEPLOY
Env2: DEV SMOKE TEST
DEV DEPLOY will be triggered by the build. DEV SMOKE TEST will be triggered after a successful deploy of DEV DEPLOY.
Again, as I mentioned, a deploy to DEV SMOKE TEST is a bit odd given that it won't be deploying anything. It will just be doing some tests.
Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events