Story #6203
closed
Can't run tests in development without first running a few steps
0%
Description
Ticket moved to GitHub: "pulp/pulpcore/1867":https://github.com/pulp/pulpcore/issues/1867
With merging [0] and [1], you can no longer just run tests in development. You have to first perform a couple steps like generating and installing the bindings. We either need docs and/or an alias that will take care of generating/installing the bindings, setting up the fixture container, etc.
[0] https://pulp.plan.io/issues/6032 [1] https://github.com/pulp/ansible-pulp/pull/223
Related issues
Updated by fao89 about 4 years ago
if the plugin is specified on pulp_install_plugins, bindings will be automatically generated https://github.com/pulp/ansible-pulp/blob/master/roles/pulp-devel/tasks/bashrc.yml#L36-L43
Updated by bmbouter about 4 years ago
I was thinking we could have the tests generate the bindings themselves as a pre-test step. Then when running any number of tests, it builds the bindings as the first step and then uses them for the duration of the test run.
This would allow us to receive this feature in the develpoment environment, on travis and github CI's, and downstream packagers too. When packaging Pulp for say Debian, you want to apply a limited number of upstream patches and you need to run the tests when you do.
Updated by daviddavis about 4 years ago
- Tracker changed from Issue to Story
- % Done set to 0
Updated by daviddavis over 3 years ago
- Related to Task #5107: Add a Makefile template to make it easier to run common plugin commands added
Updated by daviddavis over 3 years ago
I believe this could/should be solved in the Makefile (see #5107).
Updated by pulpbot over 2 years ago
- Description updated (diff)
- Status changed from NEW to CLOSED - DUPLICATE
.