Bamboo Concepts: Difference between revisions
(→Plan) |
(→Stage) |
||
| Line 13: | Line 13: | ||
{{Internal|Bamboo Operations#Plan_Operations|Plan Operations}} | {{Internal|Bamboo Operations#Plan_Operations|Plan Operations}} | ||
=Stage= | |||
Each stage within a [[#Plan|plan]] represents a step within your build process. A stage may contain one or more [[#Job|jobs]] which Bamboo can execute in parallel. | Each stage within a [[#Plan|plan]] represents a step within your build process. A stage may contain one or more [[#Job|jobs]] which Bamboo can execute in parallel. | ||
Revision as of 17:48, 7 December 2018
Internal
Project
Projects allow you to easily group and identify plans which are logically related to each other.
Plan
A build plan. It defines everything Bamboo needs to know to about the build process. Each plan has a Default job when it is created. More advanced configuration options, including those for plugins, and the ability to add more jobs will be available after creating this plan. A plan belongs to a project.
Stage
Each stage within a plan represents a step within your build process. A stage may contain one or more jobs which Bamboo can execute in parallel.
Job
Default Job
Repository
One or more repositories can be added to a plan. The repositories will then be available to every job in the plan. The first repository in the list is the plan’s default repository. The repositories to which a trigger applies can be selected in respective trigger's configuration.
Repository Types
Git
In general, use Git repositories, which allow SSH authentication.
GitHub
GitHub won't allow SSH authentication.