← Back to issue list

add the typical environment variables to any interactive session, like with `--debug`

View original Github issue

Metadata

Project
rockcraft
Number
#428
Type
issue
State
open
Author
ca-scribner
Labels
—
Created
Updated
Closed
—

Current evaluation

Rockcraft debug and shell sessions omit step-specific CRAFT_* variables; the open, untriaged request overlaps the still-open craft-application issue #435.

Suggested action: needs triage

Reason: The request clearly identifies CRAFT_PART_BUILD, CRAFT_PRIME, and similar variables that should be present in interactive sessions. Shared craft-application code currently launches these sessions through _launch_shell without those variables, while upstream issue #435 tracks the same capability; this issue has no labels, maintainer response, or other evidence of triage.

Evaluated by: mr-cal-bot

Impact: 44 Quick Win: 12 Complexity: 62 Confidence: 88 Actionability: 73

Issue body

### What needs to get done Whenever the user is dropped into an interactive session (for example, when a build error occurs during `rockcraft pack --debug`), include all environment variables that would normally exist at that stage in the build. For example, if debugging happens because part `xyz` failed, you should have `CRAFT_PART_BUILD=/root/parts/xyz/build`, `CRAFT_PRIME=/root/prime`, etc ### Why it needs to get done For a user that is debugging, they want to debug exactly where the script left off. Without these environment variables, they need to set them manually to debug their own scripts. This is both tedious and leads to errors

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 44
Quick Win: 12
Complexity: 62
Confidence: 88
Actionability: 73
needs triage Rockcraft debug and shell sessions omit step-specific CRAFT_* variables; the open, untriaged request overlaps the still-open craft-application issue #435.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 12
Complexity: 50
Confidence: 70
Actionability: 80
needs triage Feature request to include CRAFT_* environment variables in interactive debug shells for easier debugging of build failures
qwen/qwen3.8-27b
Impact: 35
Quick Win: 19
Staleness: 78
Complexity: 45
Confidence: 62
Support Request: 10
needs triage Feature request to include build-stage env vars (CRAFT_PART_BUILD, CRAFT_PRIME, etc.) in the interactive shell dropped on `--debug` build failure. No labels, no maintainer comments, no assignee; untriaged for ~2.7 years.
qwen/qwen3.6-35b-a3b
Staleness: 90
Complexity: 20
Confidence: 80
Support Request: 10
close stale Request to automatically populate standard environment variables in interactive debug shells to simplify script debugging. The issue remains unlabelled and has seen no maintainer engagement or comments in over two years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 20
Confidence: 85
Support Request: 10
needs triage Request to automatically populate typical build environment variables when entering interactive debug sessions. Currently unlabelled and awaiting maintainer assessment.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 20
Confidence: 85
Support Request: 10
close stale Feature request to automatically populate standard build environment variables when entering interactive debug sessions. Currently unlabelled and inactive for over two years with no maintainer feedback.

Update history

No update history recorded yet.

Related work

  • Blocked By: craft-application#435 (confidence 93%)

    The shared lifecycle command implements --debug, --shell, and --shell-after, and its open upstream issue requests the same step-specific CRAFT_* environment.

Related issues

Issue Project State Summary Similarity
#253 add --debug option like other `*craft` tools rockcraft closed Rockcraft already supported --debug via merged PR #224 (ffb57d58); the reporter had an outdated install, and both top-level and pack invocation forms work.
73%