orange-ability-181208/12/2023, 9:20 PM
locally, and kaniko remotely). My goal is that I want an action to download/clone another repo, run (in effect)
, and then have the outputs be available to other build tasks in my garden graph. I've run into a couple dead-ends so far though: 1. I tried just using "Build exec", which works if you don't sandbox anything which would be the more desirable way of working. Furthermore, this is not not ideal for running in CI and doesn't work in most cases. First, my CI runner is using the
image which is good for running garden, but not so much for my own toolchain and may actually be incompatible (for instance this image is on alpine). I could make my own image but then it would be a weird hybrid and hard to maintain. Without that concern it would be better just to run exactly the same build container locally and in CI. 2. So I tried running the builds inside of a Pod in the cluster (whether that is local minikube or remote GKE). The problem here is that there is no Build type for running in an exec-like command in a pod (like
for the Run action type). Using Run kubernetes-pod works, but the semantics around passing data between actions is only really set up for Build action types. I can output an artifact but AFAIK there is no good way to get this into the Build container workspace. So I think my feature request would be Build types for kubernetes-pod and kubernetes-exec. Would this be a difficult thing to add?
quaint-dress-83108/14/2023, 2:02 PM
image? I will ask for @big-spring-14945's help here since he's the genius behind those.
orange-ability-181208/14/2023, 3:00 PM
quaint-dress-83108/14/2023, 3:54 PM
orange-ability-181208/14/2023, 5:44 PM
quaint-dress-83108/15/2023, 11:28 AM