Skip to main content

Run Diffs Between Failed and Last Successful Run

Feature Requests

Problem: When something breaks, it’s not always clear what changed that caused the regression.
Request:
Enable comparison between the last successful run and the current failed run — e.g., changed plan, code diff, or commit hash context.
Impact: Speeds up debugging by giving engineers the “what changed” view directly in the UI.

Status: ⬆️ Gathering votes1 comment

Log in to comment and vote

Comments1

  • Natalia Gazda

    Team•

    Aug 5, 2025

    Hey Harrison!

    Thanks for the detailed feedback! I understand the debugging challenge you're facing when runs fail.

    You can already access this information through our existing features:
    - Each run displays its commit hash and links directly to your VCS where you can see the code diff
    - The run history shows the complete log with plan output for comparison
    - The Resources view tracks which run last modified each resource

    For the specific comparison workflow you're describing, you can:
    1. Click on the commit hash in your failed run to see what changed in the code
    2. Navigate to the previous successful run to compare plan outputs
    3. Use the Resources view to see which resources were affected

    This approach leverages your existing VCS tools (GitHub/GitLab/etc.) which already excel at showing diffs and changes. Rather than duplicating this functionality, we've focused on making it easy to navigate between Spacelift and your VCS for the full context.

    If you're finding this workflow cumbersome, could you share more details about:
    - How often this debugging scenario occurs for your team?
    - What specific information beyond the code diff and plan comparison would be most valuable?
    - Whether your VCS integration is working smoothly for accessing commit information?

    This helps us understand if there's a deeper workflow issue we should address.