global permission
Glossary
- activity log
- agent
- agent-specific capability
- artifact
- authors in Bamboo
- build
- build activity
- build duration
- build log
- build queue
- build result
- build telemetry
- capability
- child
- committer
- custom capability
- default repository
- elastic agent
- elastic Bamboo
- elastic block store
- elastic image
- elastic instance
- executable
- favorites
- global permission
- job
- label
- local agent
- parent
- permission
- plan
- plan permission
- projects in Bamboo
- queue
- reason
- remote agent
- remote agent supervisor
- requirement
- shared capability
- stage
- Stock images
- task
- triggering
- watcher
On this page
Related content
- Configuring a job's build artifacts
- Bamboo Best Practice - Sharing artifacts
- How to access artifacts that are only available locally on the Bamboo Agents
- Artifacts in Bamboo Server
- Bamboo artifact definition syntax examples
- Viewing a build's artifacts
- Automatically archive build artifacts to Amazon's S3 storage
- Artifacts don't copy to the second stage if the first task is NOT a VCS checkout task
- Artifact handlers
- Bamboo Artifact Handlers - Use Case Scenarios
A global permission is the ability to perform a particular operation in relation to Bamboo as a whole.See Granting global permissions to users or groups.
See also plan permission.
Last modified on May 7, 2012
Related content
- Configuring a job's build artifacts
- Bamboo Best Practice - Sharing artifacts
- How to access artifacts that are only available locally on the Bamboo Agents
- Artifacts in Bamboo Server
- Bamboo artifact definition syntax examples
- Viewing a build's artifacts
- Automatically archive build artifacts to Amazon's S3 storage
- Artifacts don't copy to the second stage if the first task is NOT a VCS checkout task
- Artifact handlers
- Bamboo Artifact Handlers - Use Case Scenarios
Powered by Confluence and Scroll Viewport.