Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking package dependencies/environments #4868

Closed
dberenbaum opened this issue Sep 19, 2023 · 0 comments
Closed

Tracking package dependencies/environments #4868

dberenbaum opened this issue Sep 19, 2023 · 0 comments
Labels
A: docs Area: user documentation (gatsby-theme-iterative) p2-nice-to-have Less of a priority at the moment. We don't usually deal with this immediately.

Comments

@dberenbaum
Copy link
Collaborator

Report

Background:
iterative/dvc#7378
iterative/dvc#6115
iterative/dvc#5758

We hear this come up regularly and it's probably time we add something to the docs about it. I think we could start with something like what's suggested in iterative/dvc#7378. Or we could show a couple different methods, like suggesting docker as a "best practice" but also showing iterative/dvc#7378 as an alternative if docker is too heavy.

A further request that has come up is to track the dependencies granularly per stage since a single package update should not necessarily trigger running the entire pipeline. Is there a way we could track the output of pip freeze like parameters?

@dberenbaum dberenbaum added p2-nice-to-have Less of a priority at the moment. We don't usually deal with this immediately. A: docs Area: user documentation (gatsby-theme-iterative) labels Oct 16, 2023
@dberenbaum dberenbaum closed this as not planned Won't fix, can't repro, duplicate, stale Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: docs Area: user documentation (gatsby-theme-iterative) p2-nice-to-have Less of a priority at the moment. We don't usually deal with this immediately.
Projects
None yet
Development

No branches or pull requests

1 participant