[Bamboo Knowledge Base]
Once you have created and configured your new deployment project and deployment environments, you can set up associated tasks for the deployment process. Bamboo allows you to execute a range of different tasks upon deployment including:
On this page:
Tasks may be added to a deployment environment during or after the environment creation process; tasks may also be edited and changed afterwards as well.
To add a task to a deployment environment:
Click on the task type that you want to use. Only tasks applicable to the deployment environment will be available for selection. The task configuration window will open, and you can configure the task according to the needs of your deployment project. Different tasks will have different requirements
Remember that capability and requirement matching is still in effect for deployment environments. If your task does not have the right capabilities it will not be executed, even if the relationship has been defined.
You can use Bamboo to deploy and manage your Java web application with Tomcat 6 or 7, without having to directly interact with Maven, Ant or write special scripts.
See Using Tomcat with Bamboo for continuous deployment.
You can use the Bamboo SCP task to upload files from Bamboo directly to a remote server as part of a Bamboo job. The SCP task is able to copy multiple files and preserves the directory structure for the copied files.
See Using the SCP task in Bamboo.
You can use Bamboo to deploy your Java web application to the Heroku cloud platform.
See Using the Heroku task in Bamboo.
msdeploy.exe
.Once all of your tasks have been configured, you may assign some or all of them to be Final Tasks. Final Tasks are always executed at the end of the build.
To assign a final task:
If you have already added some tasks to an environment, then they can be easily changed at a later stage. To edit environment tasks: