mdepaulo@redhat.com
mdepaulo@redhat.com- Registered on: 02/25/2019
- Last connection: 01/20/2020
Issues
- Assigned issues: 38
- Reported issues: 105
Projects
- Pulp (Developer, Private Access, Contributor, 02/25/2019)
- RPM Support (Developer, Private Access, Contributor, 02/25/2019)
- Puppet Support (Developer, Private Access, Contributor, 02/25/2019)
- Docker Support (Developer, Private Access, Contributor, 02/25/2019)
- Python Support (Developer, Private Access, Contributor, 02/25/2019)
- Packaging (Developer, Private Access, Contributor, 02/25/2019)
- Crane (Developer, Private Access, Contributor, 02/25/2019)
- OSTree Support (Developer, Private Access, Contributor, 02/25/2019)
- Debian Support (Developer, Private Access, Contributor, 02/25/2019)
- Nectar (Developer, Private Access, Contributor, 02/25/2019)
- External (Developer, Private Access, Contributor, 02/25/2019)
- File Support (Developer, Private Access, Contributor, 02/25/2019)
- Infrastructure (Developer, 02/25/2019)
- Ansible Plugin (Developer, Contributor, 02/25/2019)
- Maven Plugin (Developer, 09/18/2019)
- Container Support (Developer, Private Access, Contributor, 12/06/2019)
- Migration Plugin (Developer, Private Access, Contributor, 01/14/2020)
Activity
01/20/2020
-
Added as part of ansible-pulp 3.0.1 Task #5863 (CLOSED - CURRENTRELEASE): Generate and use a pulpcore constraints file in ansible-pulp
-
Added in time for ansible-pulp 3.0.1. Task #5892 (CLOSED - COMPLETE): ansible-pulp CI needs to test micro updates to Pulp 3A proposed solution is:
1. Manually build & upload a Pulp 3.0.0 container, like molecule builds (VM-like, systemd + all service in 1 container), to quay.io.
2. Have that pulled and tested against in a new CI test case. -
ansible-pulp 3.0.1 has this. Story #5891 (CLOSED - CURRENTRELEASE): As a user, I can use ansible-pulp to perform a micro updat...This task is to cover the use-case of a user having say Pulp 3.0.0 installed, but running ansible-pulp to update it to 3.0.1.
Required changes that have been identified:
1. Providing a variable on whether to update pulp or not during...
01/17/2020
-
-
Sorry you ran into this issue,· Commented on issue
I'm almost certain the problem is that you need to set this variable, which we document but is easy to miss:
pulp_use_system_wide_pkgs: true
Please try that.
If it works, I am open to ideas on how...
01/15/2020
-
-
I'm assigning it to myself, since I am coordinating much of this. Story #5762 (ASSIGNED): [Epic] CI ImprovementsTracking Epic for improvements to the CI, including for non-plugin-template CI like ansible-pulp & pulp-operator.
h2. Problems
There are two problems I can see wit the testing and CI/CD situation for pulpcore and its plugins.
h3... -
Implemented in:
https://github.com/pulp/plugin_template/pull/164
Update to Ubuntu 18.04 as test environment #164
By dalley. Task #5156 (CLOSED - CURRENTRELEASE): Update travis to run on ubuntu b18.04 -
Story #5996 (NEW): As a user, I can easily stop/start/restart all Pulp services on a box via a sy...We should do this:
http://alesnosek.com/blog/2016/12/04/controlling-a-multi-service-application-with-systemd/
To:
1. Provide a better user experience.
2. Ensure that if the order of starting the Pulp services ever becomes significa... -
mdepaulo@redhat.com wrote:
> This is waiting on https://pulp.plan.io/issues/5890 to be figured out in greater detail.
It is still being figured out, but is proceeding along, and we should proceed with the current design. Task #5768: ansible-pulp CI needs a more time efficient test matrixThe current plan for ansible-pulp is for it to be rolling release. Thus, it will use different codepaths for 3.0 vs master (3.1) branches.
This is currently done by testing pulpcore via pip (3.0) and master (source_dir), as well as 0....
Also available in: Atom
.