I haven’t used pipenv, but I’m assuming you’re attempting to run a regular make command, that I’m guessing does some python things that you want to ensure occurs within the context of the python virtualenv setup by pipenv.
maybe throw a quick
- run:
command: |
which make
in ahead of your pipenv run commands, to confirm if make is installed in the python image.
So, again, having not use pipenv maybe there’s some initialisation to be done, as each run command is a separate shell being executed.
Maybe this is where you do an environment exploration, I do this all the time, I find it helps, something along that line, so if you
- run:
command: |
which make
pipenv run which make
echo $PATH
pipenv run echo $PATH
export
I tend to do this just to confirm the assumptions that I have. I’ve found it helps maybe at least steer you in the right direction. I actually have an alias yaml snippet with a bunch of these commands in there and I can then just drop in this anchor where I need to fault find things, just before and after problem commands etc.
<<: *explore_environment
I can’t wait to try it out with orbs that are present in 2.1, so I don’t have to include the long list of commands everytime and also to share across repos.
Thanks for your help, @grahamw! Here’s the output of that environment exploration:
#!/bin/bash -eo pipefail
which make
pipenv run which make
echo $PATH
pipenv run echo $PATH
/usr/bin/make
/usr/bin/make
/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
No sorry, that’s weird. Maybe rerun the build with SSH and execute the commands manually to debug further. I’ve barely used pipenv, so I don’t know why it’d be complaining about not found in path when then which command works. Just make sure all the environment variables look right before you, though I think they are still set when you use the rebuild with SSH.
Oh, and just to cover off, you don’t have a typo in the name of your make target your executing with the pipenv run command compared to the makefile in that directory do you?