tkn pac describe
Describe a Pipelines-as-Code Repository and show detailed information about its associated PipelineRuns.Synopsis
Description
Thedescribe command provides detailed information about a Repository CRD including:
- Repository metadata (name, namespace, URL)
- All PipelineRuns associated with the repository
- Run status, timing, and links
- Failure analysis - Shows last 10 lines of failed tasks with error highlighting
- Optional Kubernetes events for debugging
Usage Examples
Arguments
Repository name (optional - prompts if not provided)
Flags
Namespace containing the repository
Show information for a specific PipelineRun only
Display timestamps as RFC3339 instead of relative time
Show Kubernetes events associated with the repositoryUseful for debugging issues that cannot be reported on the Git provider interface
Output Example
Basic Output
With Failure Details
When the last PipelineRun failed, error details are automatically shown:With Events
Targeting Specific PipelineRun
Column Descriptions
| Column | Description |
|---|---|
| STATUS | PipelineRun status with color coding |
| EVENT | Event type (pull_request, push) |
| BRANCH | Target branch name |
| SHA | Commit SHA (first 7 characters, clickable) |
| STARTED | When the PipelineRun started |
| DURATION | Total execution time |
| NAME | PipelineRun name (clickable to logs) |
Status Colors
The output uses colors to indicate status:- Green - Succeeded
- Red - Failed
- Yellow - Running, Pending
- Gray - Cancelled, Skipped
Clickable Links
In modern terminals, links are clickable:- SHA - Opens commit in Git provider
- NAME - Opens PipelineRun logs in console/dashboard
Failure Analysis
When a PipelineRun fails,describe automatically:
- Identifies failed tasks
- Extracts last 10 lines of logs from each failed task
- Highlights error patterns:
ERRORFAILUREFATALFailed- Exit codes
Error Highlighting
Error keywords are highlighted in red for easy identification:Kubernetes Events
With--show-events, see cluster-level events:
Event Types
- Normal - Standard operations (Started, Running, Succeeded)
- Warning - Issues or failures
Event Sources
tekton-controller- Tekton Pipeline controllerpipelinesascode-controller- PAC controllerkubelet- Kubernetes node agent
Common Events
| Reason | Description |
|---|---|
| Started | PipelineRun execution started |
| Running | Tasks are executing |
| Succeeded | PipelineRun completed successfully |
| Failed | PipelineRun failed |
| PodScheduled | Pod scheduled on node |
| Pulling | Pulling container image |
| Pulled | Image pulled successfully |
Event Limit
Shows up to 50 most recent events to avoid overwhelming output.Time Formats
Relative Time (Default)
RFC3339 Format (—use-realtime)
Common Workflows
Debug Failed Pipeline
Check Specific Run
Monitor Repository Activity
Compare Runs Across Repositories
Troubleshooting
Repository Not Found
- List repositories:
tkn pac list - Check namespace:
tkn pac list -A - Verify spelling
No PipelineRuns
If repository has no runs:- Trigger a run by creating a PR or pushing code
- Check webhook configuration:
tkn pac webhook add - Verify
.tekton/directory exists in repository
Target PipelineRun Not Found
- List available runs:
tkn pac describe myorg-app - Check PipelineRun name:
kubectl get pr - Verify it belongs to this repository
Events Not Showing
- Events expired (usually kept for 1 hour)
- No recent activity
- Insufficient RBAC permissions to view events
Permission Denied
Environment Variables
Tekton Dashboard URL for clickable linksExample:
Related Commands
tkn pac list- List all repositoriestkn pac logs- View full PipelineRun logstkn pr describe- Tekton CLI for PipelineRun details