I recently added a reusable github action to ansible-lint release pipeline that makes a pull-request on homebrew recipe that bumps its version. https://github.com/ansible/ansible-lint/pull/2982/files
This worked perfectly from the first attempt and now we do know that we don't need to wait for someone to remember to update ansible-lint recipe.
While we do have a pipeline that uses packit service to test that rpm packaging is not broken from incoming pull requests, we do not have any automated way to trigger RPM packaging an update for fedora when we release a new version.
Would it be possible to get a similar action that we can chain on our release pipeline?
-- Cheers, Sorin Sbarnea Ansible DevTools Team Lead, Red Hat
V Sat, Feb 11, 2023 at 09:16:04AM -0800, Sorin Sbarnea napsal(a):
I recently added a reusable github action to ansible-lint release pipeline that makes a pull-request on homebrew recipe that bumps its version. https://github.com/ansible/ansible-lint/pull/2982/files
This worked perfectly from the first attempt and now we do know that we don't need to wait for someone to remember to update ansible-lint recipe.
While we do have a pipeline that uses packit service to test that rpm packaging is not broken from incoming pull requests, we do not have any automated way to trigger RPM packaging an update for fedora when we release a new version.
Would it be possible to get a similar action that we can chain on our release pipeline?
I think there are legal and techincal obstacles:
A packager is personally responsible for reviewing the imported sources. If you delegated the releases into Fedora to GitHub, you would need an agreement with Microsft that they will abide by the license compliance.
Then you would need to authorize the GitHub infrustructure to updates dist-git repository in you name. I guess you do not want to entrust your Fedora credentials to GitHub machinery.
-- Petr
packaging@lists.fedoraproject.org
-
Petr Pisar -
Sorin Sbarnea