- Login: semyers
- Email: email@example.com
- Registered on: 10/20/2015
- Last connection: 01/30/2018
|Container Support||Private Access, Contributor||12/06/2019|
|Crane||Private Access, Contributor||10/20/2015|
|Debian Support||Private Access, Contributor||10/20/2015|
|Docker Support||Private Access, Contributor||10/20/2015|
|File Support||Private Access, Contributor||07/17/2017|
|Migration Plugin||Private Access, Contributor||01/14/2020|
|Nectar||Private Access, Contributor||10/20/2015|
|OSTree Support||Private Access, Contributor||10/20/2015|
|Packaging||Private Access, Contributor||10/20/2015|
|Pulp||Private Access, Contributor||10/20/2015|
|Puppet Support||Private Access, Contributor||10/20/2015|
|Python Support||Private Access, Contributor||10/20/2015|
|RPM Support||Private Access, Contributor||10/20/2015|
Applied in changeset commit:pulp|bbcdb7c378d0784f0bf12a5e870b1eb06acb3ec1.
Task #2249 (MODIFIED): Document platform Django app layoutThe Pulp developer documentation needs to be updated for 3.0. This should include:
These should go in the platform developer docs
- The location and organization of the pulp.app Django application
- How the settings.py file us...
Bonus points for passing py.test commandline flags through, like `psmash --verbose`.
Super bonus points for making psmash autocomplete based on the contents of `pulp_smash/tests/`, so you can use tab completion to make it even easier to... Story #2706: As a developer, I can easily run a subset of pulp smash tests.Currently, the `psmash` alias in our vagrant env run all the pulp smash tests. It is easy to manually invoke pulp smash to only run a subset of those tests (e.g `py.test pulp_smash/tests/rpm/` in the pulp-smash dir to just run rpm tests)...
The only major blocker for this that I can see is the potential virt-in-virt problem. Our jenkins workers are currently spawned in an openstack env, so if we aren't able to do nested virtualization we may not be able to use libvirt for t... Task #2705: Create a jenkins job that runs pulp smash in vagrantRecent discussions, focused on improving the reliability of our development environment, spawned the idea that it would be great to run pulp-smash within the current vagrant dev environment to ensure that the environment itself is being ...
I took a quick stab at adding a similar block to install the pulp_file plugin into its own VM:
diff --git a/ansible/roles/dev/tasks/main.yml b/ansible/roles/dev/tasks/main.yml
index eab0c9b..c2c6a06 100644
--- a/ansible/roles/de... Task #2702: Install Plugins into Pulp 3 development envI [recently added a task](https://github.com/pulp/devel/commit/3a49e1325e0ea7fac3281b510a45b78493196bc8#diff-c674e6be1d4fd8bed7f77bad58146d18) to the 3.0 dev playbook to install pulp_file into the platform virtualenv on install. As seen ...
Also available in: Atom