Skip to content

Conversation

msarahan
Copy link

I did this as part of some work on generating pinning conda packages. I'm putting this up as a draft because I need to pause on this particular effort and get a minimal viable product working of the other new tool (currently on internal gitlab).

Ideally, when we need to update dependencies for any repo, we'll be able to:

  1. Run RDFG, which will output recipe.yaml and conda_build_config.yaml
  2. Run my new tool, which will generate pinned environments and run_constraints conda packages
  3. Add the run_constraints conda packages to build, host and test sections, with their version pinned to whatever we just created

This will centralize expression of dependencies in dependencies.yaml, rather than sometimes needing to update recipe.yaml or CBC.yaml manually.

The goal is to have a shared action that orchestrates all of these actions, which can be scheduled as desired by projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant