This repository has been archived by the owner on Feb 6, 2024. It is now read-only.
Remove .short_path references
#26
Labels
Comments
mattmoor
added a commit
that referenced
this issue
Sep 20, 2017
This hinders two things: 1. Separate `bazel build` and running via `bazel-bin/...` (vs. `bazel run`) 1. Embedding these scripts into other actions. This also changes the tool references from `.par` to the `py_binary` directly as this should improve portability to Windows. Fixes: #26
mattmoor
added a commit
that referenced
this issue
Sep 21, 2017
This hinders two things: 1. Separate `bazel build` and running via `bazel-bin/...` (vs. `bazel run`) 1. Embedding these scripts into other actions. This also changes the tool references from `.par` to the `py_binary` directly as this should improve portability to Windows. Fixes: #26
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I recently replaced the use of
f.short_pathall overdocker_buildwith_get_runfile_pathto make it so that the scripts produced by things like:dev.createcan be built and run separately.rules_k8sexhibits the same symptom as the broken before picture, we should apply the same fixes here so that higher-level rules can bundle our actions into higher-level actions.This links to both of my PRs so far fixing this class of issue.
The text was updated successfully, but these errors were encountered: