Wolf Vollprecht

Currently when adding multiple tests, we create one environment per test. This can be a bit slow, especially when the tests have the same dependencies. For that case, it could...

We currently parse downstream tests (and serialize them) but we do not execute them. To execute a downstream test, we need to resolve for the downstream package (with our current...

Write documentation & CEP for all the Jinja functions and variables

1

It would be good to have docs for all Jinja variables and also a CEP. There are some features that have little documentation in conda-build, like `pin_compatible` and where it...

I would love to understand how we can (re-)use the `rattler` Python bindings and make them interoperable with `py-rattler-build`.

The test subcommand should also receive `-c channel` arguments and default to the ones found in the `rendered_recipe.yaml` instead of some default value of `conda-forge` as is currently the case.

We were discussing today what the rendered YAML should look like. - [ ] we should add a schema version and not render default values - [ ] Rename the...

Improve our bash preamble for better error reporting and less noise

1

Our bash preamble currently only sources the `build_script_env.sh` file. `set -x` is relatively noisy. We could instead install an error trap and return the line number where the script was...

Should we allow the creation of empty directories?

1

The `paths.json` allows for a `directory` path type. This is only useful for creating empty directories. Sometimes it might be desirable for a package to create an empty directory, for...

rattler-build is fast, that's nice! But the CLI isn't as sharp as it could be. Here is a list of issues from the top of my head: - `rattler-build build`...

We have the render only flag but the output is not really fixed. I think some JSON based rendered form of the recipes might be good.