[Bamboo Knowledge Base]
Creating a deployment project from a plan is easy with Bamboo.
A deployment is a container that holds:
To create a new deployment project you must:
If you are using plan branches, you will also need to associate the deployment with the plan branch. The plan branch represent a build for a branch within the version control system that inherits the configuration defined by the parent plan. Any new branch created is automatically built and tested using the same build configuration as the parent. When the plan branch build succeeds, it can be merged back into master.
Learn more about Deployments from branches.
On this page:
To create a new deployment project:
Complete the 'Setup deployment project' screen using the following fields:
Field | Description | Optional? |
---|---|---|
Name | The name of your deployment project | |
Description | A brief description of your deployment project | |
Source Build Plan | The name of the plan you wish to associate with the deployment project Hint: This field identifies the source of your deployment artifacts | |
Default plan branch | The plan branch that you wish to deploy. Bamboo will auto detect available plan branches for you. Choose a plan from the drop down menu. |
Bamboo allows you to edit the details of an existing deployment project.
To edit the details of an existing deployment project:
Complete the 'Update deployment project' screen using the following fields:
Field | Description | Optional? |
---|---|---|
Related Build Plan | The name of the plan you wish to associate with the deployment project Hint: This field identifies the source of your deployment artifacts | |
Name | The name of your deployment project | |
Description | A brief description of your deployment project | |
Default plan branch | The plan branch that you wish to deploy. This option will only display if your plan has a valid branch, as described above |
Bamboo's release naming configuration allows you to control:
To configure your release naming strategy:
Complete the 'Release naming' screen using the following fields:
Field | Description | Optional? |
---|---|---|
Next release name | The identification for the next release version that Bamboo will create by replacing the ${bamboo.buildNumber} term with the numbering strategy of your choice. For example 1.0-m1. | |
Automatically increment with each new release | Numbers: Check this box to automatically increment the last number in the release string. Variables: You may set Bamboo to increment release numbers according to a global variable. The global variables available will appear as part of the drop down menu in the 'Next release name field', however this field must be checked to activate global variable functionality. Available global variables will appear in the drop down menu when the 'Auto increment global variables' box is checked. | |
Preview | A preview of the release naming strategy. Note: A preview may not always be available |
Bamboo gives you control over who has permission to View and Edit aspects of your deployment project.
To configure your permission strategy:
Click the Add User or Add Group button to search for and add, users or groups