Persist python dependencies (pip/pipenv installs) in Workflows using Workspaces



I’m finding myself forced to implement workflows so that I can take advantage of organization-wide contexts.

But persisting pip and pipenv installed dependencies from one job to the next (to avoid reinstalling everything in every job) doesn’t seem too straightforward, since the workspaces are off-container and persisted paths appear under /tmp/<workspace-name>/.

Are there existing “best practices” or conventions for doing this so I can avoid hacky solutions?

p.s. I am caching my dependencies successfully and happily, but I assume there is no way to take advantage of these across jobs.


This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.