Task #6032: As a developer, I can run functional tests locally - Pulp

Actions

Send by e-mail Copy link

Task #6032

closed

As a developer, I can run functional tests locally

Added by fao89 almost 5 years ago. Updated over 4 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

fao89

Category:

Installer - Moved to GitHub issues

Sprint/Milestone:

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

Yes

Sprint Candidate:

Yes

Tags:

Sprint:

Sprint 65

Quarter:

Description

After #6020
The installer should be able to generate bindings for plugins, allowing the user to run functional tests locally

Related issues

Actions

Copy link

Updated by fao89 almost 5 years ago

Follows Task #6020: Update plugin_template tests to use bindings added

Actions

Copy link

Updated by dkliban@redhat.com almost 5 years ago

The installer's devel role should just install bindings from PyPI.

Actions

Copy link

Updated by dkliban@redhat.com almost 5 years ago

Developers working on a new plugin would not benefit from the installer installing bindings from PyPI. A developer would benefit from having a command that quickly generates python bindings and installs them into the virtualenv. The bindings could be build using the generate.sh script from pulp-openapi-generator repo. A helper function should be added called 'pbindings'. This function should generate the bindings for all the plugins installed and then install them into the virutalenv.

Actions

Copy link

Updated by daviddavis almost 5 years ago

Groomed changed from No to Yes
Sprint Candidate changed from No to Yes

Actions

Copy link

Updated by daviddavis almost 5 years ago

Sprint set to Sprint 64

Adding to the sprint as part of #6020.

Actions

Copy link

Updated by mdepaulo@redhat.com almost 5 years ago

As the ansible-pulp maintainer, I agree.

Do note that the devel role is tested in CI as part of the ansible molecule "source" scenario. It can lengthen the time to run the CI (and for pulplift to provision a devel box.) We have multiple tasks to improve the ansible-pulp CI performance, this may exacerbate their need:
https://pulp.plan.io/issues/5762

Actions

Copy link

Updated by bmbouter almost 5 years ago

Having this available for developers would be great. Typically on user systems the Pulp server bits go on one system, and the client bindings get installed to a user's local system.

pbindings sounds great. Maybe you could run:

pbindings pulpcore install to install the publpcore bindings
pbindings pulpcore uninstall to uninstall the pulpcore bindings

Also maybe we could have it preform an uninstall + install with: pbindings pulpcore reinstall

Actions

Copy link

Updated by bmbouter almost 5 years ago

Subject changed from As a user I can run functional tests locally to As a developer, I can run functional tests locally
Tags deleted (~~Pulp 3 installer~~)

Retitling to reflect the developer focus of the story. Also removed the installer tag since it would not be in the installer.

Actions

Copy link

Updated by dkliban@redhat.com almost 5 years ago

Tags Pulp 3 installer added

We actually use the installer's pulp-devel role for the dev environments. This change should be added here[0]. I am adding back the installer tag.

[0] https://github.com/pulp/ansible-pulp/blob/master/roles/pulp-devel/templates/alias.bashrc.j2

Actions

Copy link

#10

Updated by bmbouter almost 5 years ago

dkliban@redhat.com wrote:

We actually use the installer's pulp-devel role for the dev environments. This change should be added here[0]. I am adding back the installer tag.

[0] https://github.com/pulp/ansible-pulp/blob/master/roles/pulp-devel/templates/alias.bashrc.j2

Perfect, thank you.

Actions

Copy link

#11