Upload README.md
Browse files
README.md
ADDED
|
@@ -0,0 +1,127 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Jenkins Error Explainer
|
| 2 |
+
|
| 3 |
+
A documentation-grounded system that explains Jenkins pipeline errors using official Jenkins documentation.
|
| 4 |
+
|
| 5 |
+
This project analyzes raw Jenkins build logs, extracts structured error signals, retrieves relevant documentation sections, and generates clear, human-readable explanations without relying on supervised training data.
|
| 6 |
+
|
| 7 |
+
---
|
| 8 |
+
|
| 9 |
+
## Motivation
|
| 10 |
+
|
| 11 |
+
Jenkins error logs are often verbose, difficult to interpret, and highly contextual.
|
| 12 |
+
There is no standardized dataset of Jenkins errors or canonical explanations.
|
| 13 |
+
|
| 14 |
+
This project addresses that gap by:
|
| 15 |
+
- Using heuristic-based error feature extraction
|
| 16 |
+
- Grounding explanations strictly in official Jenkins documentation
|
| 17 |
+
- Avoiding hallucinated or unsafe advice
|
| 18 |
+
|
| 19 |
+
---
|
| 20 |
+
|
| 21 |
+
## What This Project Does
|
| 22 |
+
|
| 23 |
+
Given a Jenkins pipeline error log, the system:
|
| 24 |
+
1. Extracts key error signals (syntax errors, missing agents, missing plugins, etc.)
|
| 25 |
+
2. Retrieves relevant sections from Jenkins documentation
|
| 26 |
+
3. Generates a structured explanation including:
|
| 27 |
+
- Error summary
|
| 28 |
+
- Likely causes
|
| 29 |
+
- Links to official documentation
|
| 30 |
+
|
| 31 |
+
---
|
| 32 |
+
|
| 33 |
+
## What This Project Does NOT Do
|
| 34 |
+
|
| 35 |
+
- Does not train or fine-tune a language model
|
| 36 |
+
- Does not rely on labeled error datasets
|
| 37 |
+
- Does not scrape community forums or StackOverflow
|
| 38 |
+
|
| 39 |
+
---
|
| 40 |
+
|
| 41 |
+
## Project Structure
|
| 42 |
+
|
| 43 |
+

|
| 44 |
+
|
| 45 |
+
## Error Categories Covered
|
| 46 |
+
|
| 47 |
+
- Pipeline syntax errors (invalid Groovy, missing braces)
|
| 48 |
+
- Missing agent or unavailable nodes
|
| 49 |
+
- Missing plugins / undefined DSL methods
|
| 50 |
+
- Missing credentials
|
| 51 |
+
- Workspace and file system errors
|
| 52 |
+
- Git / SCM authentication failures during checkout
|
| 53 |
+
|
| 54 |
+
---
|
| 55 |
+
|
| 56 |
+
## Model Usage
|
| 57 |
+
|
| 58 |
+
This project does not train or fine-tune any machine learning models.
|
| 59 |
+
|
| 60 |
+
Pre-trained sentence embedding models are used solely for semantic retrieval
|
| 61 |
+
over Jenkins documentation. No Jenkins error logs are used for training.
|
| 62 |
+
|
| 63 |
+
This design avoids the need for labeled datasets and ensures predictable,
|
| 64 |
+
reproducible behavior.
|
| 65 |
+
|
| 66 |
+
---
|
| 67 |
+
## Example
|
| 68 |
+
|
| 69 |
+
**Input:**
|
| 70 |
+
Raw Jenkins console output containing a groovy syntax error.
|
| 71 |
+
|
| 72 |
+
**Output:**
|
| 73 |
+
Error Category:
|
| 74 |
+
groovy_syntax_error
|
| 75 |
+
|
| 76 |
+
Error Summary:
|
| 77 |
+
The pipeline failed due to a Groovy syntax error, most likely caused by an invalid or incomplete Jenkinsfile.
|
| 78 |
+
|
| 79 |
+
Likely Causes:
|
| 80 |
+
- Missing or mismatched braces in the Jenkinsfile
|
| 81 |
+
- Invalid declarative pipeline structure
|
| 82 |
+
|
| 83 |
+
Relevant Documentation:
|
| 84 |
+
- pipeline_syntax.txt (https://www.jenkins.io/doc/)
|
| 85 |
+
- using_a_jenkinsfile.txt (https://www.jenkins.io/doc/)
|
| 86 |
+
- using_a_jenkinsfile.txt (https://www.jenkins.io/doc/)
|
| 87 |
+
- using_a_jenkinsfile.txt (https://www.jenkins.io/doc/)
|
| 88 |
+
- using_a_jenkinsfile.txt (https://www.jenkins.io/doc/)
|
| 89 |
+
|
| 90 |
+
## Design Principles
|
| 91 |
+
|
| 92 |
+
- Documentation-first retrieval (RAG)
|
| 93 |
+
- Heuristic-driven error understanding
|
| 94 |
+
- Explicit handling of uncertainty
|
| 95 |
+
- Reproducible and explainable behavior
|
| 96 |
+
|
| 97 |
+
---
|
| 98 |
+
|
| 99 |
+
## Future Extensions
|
| 100 |
+
|
| 101 |
+
- Jenkinsfile explanation support
|
| 102 |
+
- Plugin-aware error analysis
|
| 103 |
+
- CLI or web-based interface
|
| 104 |
+
- Version-aware documentation indexing
|
| 105 |
+
|
| 106 |
+
---
|
| 107 |
+
|
| 108 |
+
## Guarantees and Limitations
|
| 109 |
+
|
| 110 |
+
This tool does NOT act as a general-purpose AI assistant.
|
| 111 |
+
|
| 112 |
+
Guarantees:
|
| 113 |
+
- Explanations are grounded in official Jenkins documentation only.
|
| 114 |
+
- Error classification is deterministic and rule-based.
|
| 115 |
+
- If relevant documentation is not found, the tool explicitly reports uncertainty.
|
| 116 |
+
|
| 117 |
+
Limitations:
|
| 118 |
+
- The tool does not attempt to fix errors automatically.
|
| 119 |
+
- It does not infer causes beyond documented Jenkins behavior.
|
| 120 |
+
- Unknown or plugin-specific errors may be reported as unsupported.
|
| 121 |
+
|
| 122 |
+
---
|
| 123 |
+
|
| 124 |
+
## Disclaimer
|
| 125 |
+
|
| 126 |
+
This project is an independent personal project and is not affiliated with or endorsed by the Jenkins project.
|
| 127 |
+
|