Add --shell-after for lifecycle steps
Metadata
Current evaluation
Implemented --shell-after via merged snapcore/snapcraft PR #2253 (commit 21cfd4750), opening a shell after the selected lifecycle step.
Resolution: closed resolved
Reason: Merged PR #2253 added build-provider support for --shell-after in commit 21cfd4750. Lifecycle code propagates the option and opens the debug shell after running the requested step.
Evaluated by: mr-cal-bot
No scores available.
Issue body
This should shell into the environment after the target step is run.
The working directory should be that of the step for the part that was just run to run.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Implemented --shell-after via merged snapcore/snapcraft PR #2253 (commit 21cfd4750), opening a shell after the selected lifecycle step. | |
| stealth/space-bunny-alpha | — | closed resolved | Implemented lifecycle --shell-after support in snapcraft#2253, committed as 21cfd4750, so builds open a shell after the selected step in that step’s working directory. | |
| stealth/space-bunny-alpha | — | closed resolved | Implemented --shell-after: merged PR #2253 (commit 21cfd4750) added build-provider support for shelling into the build env after a lifecycle step; feature remains in snapcraft/parts/parts.py. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a recorded fix or linked PR after roughly eight years of inactivity; no --shell-after implementation was found. | |
| qwen/qwen3.6-35b-a3b | — | — | The --shell-after flag request for lifecycle steps was closed without implementation. Zero comments and no resolution details indicate the feature was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Request to add --shell-after for lifecycle steps was closed without implementation. Zero comments and no resolution details indicate the feature was abandoned or superseded. | |
| qwen/qwen3.6-35b-a3b | — | — | The request to add a --shell-after flag for lifecycle steps was closed without implementation. No comments or pull requests were created, indicating the feature was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | The --shell-after flag request for lifecycle steps was closed without implementation. Lack of comments and extended inactivity indicate the feature was abandoned. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#2253
(confidence 100%)
Merged PR whose commit 21cfd4750 added --shell-after support.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1782768 Add --shell for lifecycle steps | snapcraft (launchpad) | closed | Feature request closed by the author's own pointer to snapcraft PR #2254, which added --shell support to build providers (commit a24d398e4); companion --shell-after landed in PR #2253. | |
| #2253 build-providers: add support for --shell-after | snapcraft | merged | Merged as 21cfd4750, adding build-provider support for --shell-after so a shell can open after the requested lifecycle step. | |
| #1823512 `snapcraft --shell` shouldn't run the lifecycle steps | snapcraft (launchpad) | open | Bare snapcraft --shell runs lifecycle actions before opening the shell. The one-line reproducer is confirmed, but the default snap command semantics and a definitive resolution are not documented. | |
| #4963 Support `--shell` and `--shell-after` for `snapcraft pack` | snapcraft | closed | Restored --shell and --shell-after for snapcraft pack via merged craft-application#436 (ab55ec81); the fix shipped in Snapcraft 8.4.1. |