Spaces:
Sleeping
Sleeping
| # CI/CD Doctor π οΈ | |
| An interactive environment where agents diagnose and fix broken CI/CD pipelines using command-based actions. | |
| ## π§ Instructions | |
| You interact with a simulated pipeline using commands. | |
| ### Available Commands | |
| - `run_pipeline` β Executes the pipeline | |
| - `view_logs` β Shows failure logs | |
| - `fix_yaml` β Fix configuration issues | |
| - `install_dependencies` β Resolves missing packages | |
| ### Objective | |
| Identify why the pipeline fails and fix it step-by-step until it passes. | |
| --- | |
| ## β Example (Easy Scenario) | |
| ### Problem: Pipeline fails due to missing dependency (`flask` not found) | |
| Step 1: | |
| ``` | |
| pipeline run | |
| ``` | |
| Step 2: | |
| ``` | |
| cat requirements.txt | |
| ``` | |
| Step 3: | |
| ``` | |
| echo "flask" >> requirements.txt | |
| ``` | |
| Step 4: | |
| ``` | |
| pipeline run | |
| ``` | |
| β Pipeline should now pass. | |
| --- | |
| ## β οΈ Rules | |
| - Always check logs before fixing | |
| - Use only available commands | |
| - Fix issues incrementally (donβt guess blindly) | |
| --- | |
| ## π― Difficulty Levels | |
| - Easy β Simple syntax/config issues | |
| - Medium β Dependency or environment problems | |
| - Hard β Multi-step failures requiring reasoning |