March 3, 2020
- S3 PRs - https://github.com/pulp/pulp_file/pull/358 - waiting on second review from dkliban or mikedep333 - https://github.com/pulp/ansible-pulp/pull/247 - waiting on review/merge from dkliban or mikedep333 - https://github.com/pulp/plugin_template/pull/188 - template - Update the Dockerfile.j2 (with conditional jinja2 logic based on a var) instead of before_install.sh.j2 - Github Actions - Feedback so far? - Next sprint, move a plugin over to Github Actions? - https://github.com/pulp/pulp_npm/pull/2 - daviddavis to propose on pulp-dev list - We’re installing pulp-smash from source. Should we switch to the pypi package? - Yes: https://pulp.plan.io/issues/6285 - Ansible check mode added to ansible-pulp CI. Will this affect runtime by much? - Ansible-pulp: CentOS 7 not tested in certain tests. - MD: I recall there being a reason several months ago. - CentOS 8 test being added, but we should check if the 8GB RAM of Travis / GHA will be used up. It would be 4 containers tested in parallel. - Mike did research into centos stream; we’re relying on 8.2. - Pulplift CI with nested virt? <https://github.com/pulp/pulplift/pull/66> - Dkliban will update ticket and make sure it’s added to the sprint https://pulp.plan.io/issues/5610 - FYI: No real progress made on branch support in ansible-pulp CI over last week due to Mike’s business / sickness. - FYI: Fixed a horrible CI bug <https://github.com/pulp/ansible-pulp/pull/249>, like the “source” scenarios installing pulp_file a 2nd time rather than pulp_rpm - No pulp_rpm / pulp_rpm_prerequisites bug slipped into a release because of this. - FYI: Be aware of other files that need to be modified, especially during PR time. - FYI: Fixed a bug <https://github.com/pulp/ansible-pulp/pull/244/files>that I had to workaround several months ago. David
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev