It’s easy enough to get info on new releases of GitLab itself (there’s an indication - if not turned off - in the admin area, an a blog with an RSS feed), but apart from the announcements of most/every new minor version of GitLab mentioning that a new version of the runner is released, I haven’t any way of finding out that a new version is released.
Is there an easy way? How do others handle keeping the runner up-to-date?
Hey @grove - following up your message here to keep the discussion in the community going - I just wanted to make sure your email was kept private.
GitLab.com uses the MailGun service for outbound emails, and I definitely don’t see a Release notification for that date that went out to you - though other project notifications have gone out before and after.
Can you audit your notifications at https://gitlab.com/profile/notifications and make sure that the notifications for https://gitlab.com/gitlab-org/gitlab-runner are set to Custom? Or if it’s set to Global - that your Global notifications include New Releases? If it is Custom, it might be worth setting them back to Global and re-setting them to Custom and see if that triggers a reset.
And one showing that “Custom” (it’s the only project having “Custom”-setting) includes “New release”
![Skærmbillede_2020-09-01_13-15-31|348x500]
(upload://9eP7r31Y3FMd6DoYVjjpaMLr7El.png)
My global notification level (that shouldn’t matter here) is set to “Participate”.
I’ve tried to change the setting from “Custom” to “Global” and back.
Is the debian package especially hairy? I have a number of machines installed via package, and my updates are run nightly via cron. And I don’t really watch it anymore, not for months now, because it always just works.I have 5 or 6 gitlabs for different groups/orgs/locations, and they all update nightly by cron.
In fact, a lot of my machines are auto-patched, and I’ve done that on a succession of machines for 20 years, and I’ve really not needed to care. Either I’m getting really great results or you’re getting uncharacteristically bad ones!
Hey, I understand the aversion. My experience with debian was brief and onomatopoetic, so I can’t comment on its reliability or validation. After 20 years on the mix I’m using, though, I can say for sure that one can have updates without breakage.
Good for you. My experience is a bit different, especially when exercising less used code paths (we do that a lot at work, and while the packages typically work, those code paths sometimes get broken in updates. As late as this saturday (where my colleagues didn’t expect to work) one of the other teams in the company I work for had a problem caused by an automatic upgrade.