Project

Profile

Help

Story #6203

Can't run tests in development without first running a few steps

Added by daviddavis 11 months ago. Updated 14 days ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

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

Related to Pulp - Task #5107: Add a Makefile template to make it easier to run common plugin commandsPOST

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by fao89 11 months 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

#2 Updated by bmbouter 11 months 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.

#3 Updated by daviddavis 11 months ago

  • Tracker changed from Issue to Story
  • % Done set to 0

#4 Updated by pulpbot 3 months ago

  • Status changed from NEW to POST

#5 Updated by daviddavis 14 days ago

  • Status changed from POST to NEW

#6 Updated by daviddavis 14 days ago

  • Related to Task #5107: Add a Makefile template to make it easier to run common plugin commands added

#7 Updated by daviddavis 14 days ago

I believe this could/should be solved in the Makefile (see #5107).

Please register to edit this issue

Also available in: Atom PDF