-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Minimalistic way of dvc pull
usage in ci/cd
#1835
Comments
Related #1487 . @puhoshville have you seen that ticket? Would be great if you read it and let us know what you think. |
It makes sense, because Steps to reproduce with Docker: FROM python
RUN apt-get remove git --yes
RUN pip install dvc
RUN mkdir -p /tmp/example \
&& mkdir -p /tmp/dvc-storage \
&& cd /tmp/example \
&& dvc init --no-scm \
&& dvc remote add -d dvc-storage /tmp/dvc-storage \
&& echo "hello" > hello \
&& dvc add hello \
&& dvc push \
&& rm -rf .dvc/cache \
&& dvc pull |
Traceback:
|
@MrOutis Got it! Thank you! Will send a fix ASAP. |
@shcheklein I think that this issue is not quite relevant to the dataset storage task. exactly same |
@puhoshville yeah, it is a simple import bug in one of unrelated parts of dvc. I have my patch going, should be ready today. Thanks for the feedback! 🙂 |
I'm using dvc pull in ci pipeline and not so long ago (after a new release) it broke due to lack of git executable in the container (python:3.6-slim-jessie). It was easily fixed by including of additional stage to Dockerfile with git-core installation, but this approach does not meet minimalistic principals of ci. I think that some dvc methods such as dvc pull need to be considered as production-ready with no additional requirements.
The text was updated successfully, but these errors were encountered: