-
-
Notifications
You must be signed in to change notification settings - Fork 421
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
doc: guidelines for PDM usage in CI #2472
Comments
What about https://pdm-project.org/latest/usage/advanced/#use-pdm-in-continuous-integration PDM is storing caches at what Feel free to contribute to the docs if there is anything unclear. |
But we use Gitlab CI, so we can't take advantage of the action, otherwise I would just have had and not bothered you 😉 |
OK. I am dying to see it. I will look at it as soon as you create it. |
btw, in the multi-stage Dockerfile example, the documentation is still using a |
I think it's OK to keep it, though we should provide a venv example too, good catch. |
See #2482 for further discussion please. |
Hi guys do you have some guidelines on how to build a package using CI and PDM? On Github and Gitlab? |
Please ask this as a Discussions question. |
Is your feature request related to a problem? Please describe.
Currently, the documentation gives no instructions for CI: what directories should be cached, or should it even be, should the pip cache be cached, what command you be used in the CI (
install
vssync
)? Inspiration can be drawn from Poetry and CI builds -- best practices, knowledge share (travisci), and discussionI am asking because I migrated our pipelines from Pipenv to PDM, and package install time doubled. With pipenv we used to cache the pip cache between jobs, but I suspect PDM is not only reliable on this. Will caching the
cache_dir
make an impact on installs in CI ? Will it on locking? (we have repos were the pdm.lock is not checked-out).Thank you.
The text was updated successfully, but these errors were encountered: