default repository
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
- 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
- How to generate a heap dump
- Analyze OutofMemory errors in Jira Server and Data Center with heap dumps
- How to capture Java Heap dumps before Full GC in Jira
- How to capture Java Heap dumps before Full GC in Confluence
- How to get a Java Heap Dump
- Generating a thread dump
- How to analyze performance diagnostics ( thread dumps, heap dumps, garbage collection logs )
- How to debug Out of Memory Heap Space
- Troubleshooting Jira performance with Thread dumps
- HeapDump generation using jmap in Jira pod fails with error: Unable to open socket file, target process <PID> doesn't respond within 10500ms or HotSpot VM not loaded
The first repository in the list of plan repositories is the Plan's Default Repository. The default repository will be automatically checked out by any new job created.
Repository specific Plan Variables, such as repository.revision.number, will point to the default repository of a Plan. To address a specific repository, you must add the name of the repository to the end of the variable as follows: repository.revision.number.product_core.
Last modified on May 24, 2016
Related content
- How to generate a heap dump
- Analyze OutofMemory errors in Jira Server and Data Center with heap dumps
- How to capture Java Heap dumps before Full GC in Jira
- How to capture Java Heap dumps before Full GC in Confluence
- How to get a Java Heap Dump
- Generating a thread dump
- How to analyze performance diagnostics ( thread dumps, heap dumps, garbage collection logs )
- How to debug Out of Memory Heap Space
- Troubleshooting Jira performance with Thread dumps
- HeapDump generation using jmap in Jira pod fails with error: Unable to open socket file, target process <PID> doesn't respond within 10500ms or HotSpot VM not loaded
Powered by Confluence and Scroll Viewport.