feat: env-specific builds - #696
Conversation
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Expose the selected environment name to build scripts (and bundling) by introducing ICP_CLI_ENVIRONMENT, and document/test the behavior end-to-end.
Changes:
- Pass
ICP_CLI_ENVIRONMENTintoscriptbuild step execution and thread the environment through build operations. - Add
-e/--environmenttoicp project bundle(defaulting toic) and verify propagation via integration tests. - Update reference docs/guides and changelog to describe the new environment variable.
Reviewed changes
Copilot reviewed 15 out of 15 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/reference/environment-variables.md | Documents ICP_CLI_ENVIRONMENT and clarifies CWD behavior for script steps. |
| docs/reference/configuration.md | Adds ICP_CLI_ENVIRONMENT to the build-script environment variable list. |
| docs/guides/creating-recipes.md | Mentions ICP_CLI_ENVIRONMENT availability in build recipe scripts. |
| docs/concepts/build-deploy-sync.md | Notes ICP_CLI_ENVIRONMENT in build scripting section. |
| crates/icp/src/canister/build/script.rs | Injects ICP_CLI_ENVIRONMENT into script build execution and adds a unit test. |
| crates/icp/src/canister/build/mod.rs | Extends build Params with an environment field. |
| crates/icp-cli/tests/deploy_tests.rs | Verifies deploy passes environment name into build scripts. |
| crates/icp-cli/tests/bundle_tests.rs | Adds coverage for bundle default environment (ic) and override behavior. |
| crates/icp-cli/tests/build_tests.rs | Verifies icp build exposes environment selection via ICP_CLI_ENVIRONMENT. |
| crates/icp-cli/src/operations/bundle.rs | Threads environment through bundle creation to builds. |
| crates/icp-cli/src/operations/build.rs | Threads environment into build execution and params. |
| crates/icp-cli/src/commands/project/bundle.rs | Adds bundle --environment flag w/ default and env-var support. |
| crates/icp-cli/src/commands/deploy.rs | Passes selected environment name into multi-canister build. |
| crates/icp-cli/src/commands/build.rs | Passes selected environment name into multi-canister build. |
| CHANGELOG.md | Records the new build-script environment variable and bundle flag. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| &Params { | ||
| path: canister_path.to_owned(), | ||
| output: wasm_output_path.to_owned(), | ||
| environment: environment.to_owned(), |
There was a problem hiding this comment.
Build output can now vary by environment, but the artifact store still has one slot per canister (artifacts.save(&canister.name, …) 18 lines down, .icp/cache/artifacts/<name>). That was safe under the reproducibility rule this PR removes from build-deploy-sync.md. Now icp canister install <c> without --wasm serves whatever was built last — so deploy -e staging then install -e local installs the staging wasm, and project bundle (defaults to ic) silently clobbers the local artifacts for every canister.
Key the artifact dir by environment, or keep a caveat in the docs in place of the deleted bullet.
There was a problem hiding this comment.
Resolution: we do not want environment-specific build caches, because that will just lead to installing stale artifacts given the same command pattern, plus change slightly how icp canister install works.
No description provided.