search

hifis-net / ansible-role-gitlab-runner

:warning: PLEASE NOTE: This role has been migrated to our hifis.toolkit collection. :warning: Ansible role for deploying GitLab-Runner. The role is optimized for use with Openstack.
https://galaxy.ansible.com/ui/repo/published/hifis/toolkit/
Other
8 stars 2 forks source link

Specify version explicitly in Debian apt pinning #92

Closed tobiashuste closed 1 year ago

tobiashuste commented 1 year ago

Ansible itself introduces apt pinning with a priority of 1001, which conflicts with our priority and apt pinning configuration. See https://github.com/ansible/ansible/commit/04e892757941bf77198692bbe37041d7a8cbf999

By specifying the version explicitly this issue is resolved without touching the Pin-Priority value.

tobiashuste commented 1 year ago

@Normo @christianhueserhzdr I have an issue here which I don't understand. As soon as a new gitlab-runner release is made available the Debian jobs fail. See https://github.com/hifis-net/ansible-role-gitlab-runner/actions/runs/3317804213.

In this change I updated the version string to the latest version. The pipeline directly succeeds. I can reproduce this locally as well but only with Debian. Does anyone have an idea what happens here?

tobiashuste commented 1 year ago

@Normo It turned out to not be as easy as increasing the pin-priority solely. I was able to make it work by specifying the version explicitly while keeping the pin-priority at 1001. Thanks for help with debugging it!

Could you please review this as well?