← Back to issue list

executor: enable application-defined environment variables

View original Github issue

Metadata

Project
craft-parts
Number
#220
Type
pull request
State
merged
Author
cmatsuoka
Labels
Created
Updated
Closed

Current evaluation

Merged. Enables application-defined environment variables during step scriptlet execution via pre-step and prologue callbacks. Code refactored to separate global and step variables. Documentation deferred until API stability.

Suggested action:

No scores available.

Issue body

Allow application-defined variables to be used during step scriptlet execution. Applications can use the pre-step callback to set step environment variables or the prologue callback to set global environment variables. Signed-off-by: Claudio Matsuoka <claudio.matsuoka@canonical.com> - [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? ----- CRAFT-1070

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Merged. Enables application-defined environment variables during step scriptlet execution via pre-step and prologue callbacks. Code refactored to separate global and step variables. Documentation deferred until API stability.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#82 executor: set step environment variables (CRAFT-272) craft-parts merged Merged after two approvals and passing CI. Adds project and part environment variables to step execution. Implementation validates names and supports custom prefixes instead of automatic transformation.
78%
#53 executor: create environment for step execution craft-parts merged Merged. Adds environment generation for step execution using built-in, plugin, and user-defined variables. Logic ported from snapcraft. Approved by two reviewers, passed CI, and added 585 lines across six files.
72%