#renovatebot — Public Fediverse posts

Технический долг — это не только legacy: как мы уменьшаем разброс решений между Go-сервисами

Когда компания растёт из одного продуктового направления в несколько, технический долг начинает выглядеть иначе. Проблема уже не в «старом коде», устаревших зависимостях или сложной поддержке legacy-системы. Долг начинает накапливаться в расхождении инженерных решений между сервисами. Для нас в QIC digital hub это особенно заметно на фоне миграции на новый Go-бэкенд. Исторически платформа развивалась на разнородном стеке: разные части системы были написаны на разных технологиях. Сейчас мы постепенно переезжаем на Go. Часть сервисов уже в проде, часть ещё на пути. Именно в такой момент легко создать новый слой техдолга поверх старого: переписать поведение на новом языке, но оставить команды один на один с десятками одинаковых инфраструктурных задач, которые каждая решает по-своему. Мы стараемся не просто переносить сервисы на новый стек, а одновременно пересобирать инженерную инфраструктуру вокруг них. В нашем случае это несколько взаимосвязанных инструментов: - go-kit — общая библиотека с переиспользуемыми инженерными решениями; - go-service-template — шаблон, который делает эти решения стандартным способом запуска нового сервиса; - shared-renovate-config — общий Renovate-конфиг с единой политикой обновления зависимостей для всех репозиториев. Ниже — честная инженерная история о том, как мы стараемся замедлить накопление нового техдолга в растущей мультидоменной платформе.

https://habr.com/ru/articles/1056628/

#golang #микросервисы #технический_долг #архитектура #рефакторинг #стандартизация #шаблонизация #управление_зависимостями #бэкенд #renovatebot

@electret nice, I‘m currently also experimenting with #k3s controlled through #ArgoCD with a self hosted #Forgejo. #renovatebot updates the helm chart of the #appOfApps each night and creates pull requests which gets validated by a #forgejorunner worklow before merging. Still at the beginning of the journey from single host docker to a cluster though.

@electret nice, I‘m currently also experimenting with #k3s controlled through #ArgoCD with a self hosted #Forgejo. #renovatebot updates the helm chart of the #appOfApps each night and creates pull requests which gets validated by a #forgejorunner worklow before merging. Still at the beginning of the journey from single host docker to a cluster though.

@guerda we operate a hosted #renovatebot - https://docs.codefloe.com/usage/renovate/

@guerda
A member of @hostsharing is working on a Forge solution that includes #RenovateBot
https://forge.sebatec.eu/sebatec-eu/forge

@guerda
A member of @hostsharing is working on a Forge solution that includes #RenovateBot
https://forge.sebatec.eu/sebatec-eu/forge

I would really like to move away from #GitHub with my projects towards #Codeberg.
I still would like to use #RenovateBot by Mend, but they don't offer it with Codeberg. Any good way to keep it running also on Codeberg?

Reposts appreciated.

#di_day

I would really like to move away from #GitHub with my projects towards #Codeberg.
I still would like to use #RenovateBot by Mend, but they don't offer it with Codeberg. Any good way to keep it running also on Codeberg?

Reposts appreciated.

#di_day

This has been what's it's all been for...

Bots raising PRs when a container is updated. I have the ability to roll back these back if something goes wrong and the same is true of OS updates.

#bootc #RenovateBot #Podman #Quadlets

This has been what's it's all been for...

Bots raising PRs when a container is updated. I have the ability to roll back these back if something goes wrong and the same is true of OS updates.

#bootc #RenovateBot #Podman #Quadlets

RE: https://mastodon.social/@connel/115382187613159005

I fixed it! I had to mount the host's podman container storage directory in my #Gitea runner but I think I'm out of the woods.

I did look at Nix but now I've got a working build pipeline, I'm hoping I'll be able to build something really cool with #RenovateBot

RE: https://mastodon.social/@connel/115382187613159005

I fixed it! I had to mount the host's podman container storage directory in my #Gitea runner but I think I'm out of the woods.

I did look at Nix but now I've got a working build pipeline, I'm hoping I'll be able to build something really cool with #RenovateBot

1/5 Heya Fed, Hint of the day for the devs out there: I was heavily reliant on Dependabot to keep my project's software dependencies versions up to date (you are keeping your dependencies up to date, right?).

Some colleagues who are deeper into OSS told me to try Renovate, but I mostly dismissed it as just alt tech.

https://docs.renovatebot.com/

#devops #renovatebot #oss #dependabot #automation #softwaremaintenance #ci #monorepo #buildtools #developerexperience #selfhosted

1/5 Heya Fed, Hint of the day for the devs out there: I was heavily reliant on Dependabot to keep my project's software dependencies versions up to date (you are keeping your dependencies up to date, right?).

Some colleagues who are deeper into OSS told me to try Renovate, but I mostly dismissed it as just alt tech.

https://docs.renovatebot.com/

#devops #renovatebot #oss #dependabot #automation #softwaremaintenance #ci #monorepo #buildtools #developerexperience #selfhosted

1/5 Heya Fed, Hint of the day for the devs out there: I was heavily reliant on Dependabot to keep my project's software versions up to date (you are keeping your dependencies up to date, right?).

Some colleagues who are deeper into OSS told me to try Renovate, but I mostly dismissed it as just alt tech.

https://docs.renovatebot.com/

#devops #renovatebot #oss #dependabot #automation #softwaremaintenance #ci #monorepo #buildtools #developerexperience #selfhosted

I should've known an alternative existed for #dependabot. 😅

#renovatebot is pretty interesting. You can run fairly quickly. And it supports #gitea and #forgejo. 😎

https://github.com/renovatebot/renovate

I should've known an alternative existed for #dependabot. 😅

#renovatebot is pretty interesting. You can run fairly quickly. And it supports #gitea and #forgejo. 😎

https://github.com/renovatebot/renovate

Neu im Forum:

renovate.json

https://t3forum.net/d/853-renovatejson

#t3academyforum #renovatebot #dependencymanagement

Neu im Forum:

renovate.json

https://t3forum.net/d/853-renovatejson

#t3academyforum #renovatebot #dependencymanagement

What I did in the last weeks (part 2):

All of my k3s clusters (and I have a few of them for $REASONS) are now running either #fluxCD or #argoCD. So everything #gitops now.

In general, I like the lightweightness of fluxCD, not having to run Redis and whatnot. But having a GUI is sometimes nice, even though the flux CLI is really easy to use and very intuitive.

And of course, #renovatebot is watching all repositories and sending merge requests to update things in the clusters. Nice!

#k3s #homelab #kubernetes #k8s #fluxCD #ArgoCD #GitOps

What I did in the last weeks (part 2):

All of my k3s clusters (and I have a few of them for $REASONS) are now running either #fluxCD or #argoCD. So everything #gitops now.

In general, I like the lightweightness of fluxCD, not having to run Redis and whatnot. But having a GUI is sometimes nice, even though the flux CLI is really easy to use and very intuitive.

And of course, #renovatebot is watching all repositories and sending merge requests to update things in the clusters. Nice!

#k3s #homelab #kubernetes #k8s #fluxCD #ArgoCD #GitOps

I'm setting up #renovate for our internal #gitlab and I can see already how much I missed this tool and how useful it will be. Should have done this way earlier 😊

#renovatebot

I'm setting up #renovate for our internal #gitlab and I can see already how much I missed this tool and how useful it will be. Should have done this way earlier 😊

#renovatebot

Playing around with #RenovateBot and its custom managers to automate #DependencyManagement PRs on #GitHub

https://www.tekovic.com/blog/use-custom-managers-in-renovate/

I am not happy that I somehow missed this https://github.com/renovatebot/renovate/pull/33991

#renovatebot #nix #flakes #nixos

I am not happy that I somehow missed this https://github.com/renovatebot/renovate/pull/33991

#renovatebot #nix #flakes #nixos

Last night this beauty of a PR got finally merged https://github.com/renovatebot/renovate/pull/31921

So when https://github.com/NixOS/nix/issues/8074 gets worked around or resolved, #renovatebot will finally bump your flake.lock 🎉

So happy to finally get this out of the door!

#NixOS #flakes #nix

Last night this beauty of a PR got finally merged https://github.com/renovatebot/renovate/pull/31921

So when https://github.com/NixOS/nix/issues/8074 gets worked around or resolved, #renovatebot will finally bump your flake.lock 🎉

So happy to finally get this out of the door!

#NixOS #flakes #nix

Managed to migrate my first #Truecharts app from #TrueNAS to #Talos.

Do this only if you need another hobby. It is definitely nothing like the comfort the TrueNAS App Catalogue and UI provided.

But i like #Kubernetes and so it is fine for me, to play around with #CertManager, #RenovateBot, #FluxCD and #VolSync. Just have to compare resource consumption now 😅

Workaround for my earlier problem:

When you want #RenovateBot to update images that are cached on an #azure container registry, it will not work because Renovate can not see new versions that have not yet been pulled and cached.

You can mitigate this by configuring a registryAlias for Renovate that points on the original registry (i.e. docker.io) where the cached images come from. Renovate will find new versions there and create Pull Requests for them.

https://docs.renovatebot.com/configuration-options/#registryaliases

#DevOps

Workaround for my earlier problem:

When you want #RenovateBot to update images that are cached on an #azure container registry, it will not work because Renovate can not see new versions that have not yet been pulled and cached.

You can mitigate this by configuring a registryAlias for Renovate that points on the original registry (i.e. docker.io) where the cached images come from. Renovate will find new versions there and create Pull Requests for them.

https://docs.renovatebot.com/configuration-options/#registryaliases

#DevOps

@jgarber maybe projects like #renovatebot could add automated warnings about 'dangerous' gems as well.

I like that idea of yours.

Maybe somebody could create an issue for that:

https://github.com/renovatebot/renovate/issues

@jgarber maybe projects like #renovatebot could add automated warnings about 'dangerous' gems as well.

I like that idea of yours.

Maybe somebody could create an issue for that:

https://github.com/renovatebot/renovate/issues

This week I have been building some #container images for e.g. #renovatebot and I must say I really dig #Chainguard and the #WolfiOS ecosystem. Building an image locally using #apko was a breeze. Building on #GitHub was easy due to their Github Action.

And the long list of packages available is nice.

And the list of CVEs in the image is really short.

I'll try to get my hands dirty with melange and try to build a Pluto package for WolfiOS...

This week I have been building some #container images for e.g. #renovatebot and I must say I really dig #Chainguard and the #WolfiOS ecosystem. Building an image locally using #apko was a breeze. Building on #GitHub was easy due to their Github Action.

And the long list of packages available is nice.

And the list of CVEs in the image is really short.

I'll try to get my hands dirty with melange and try to build a Pluto package for WolfiOS...

Can anyone recommend a good tutorial on #RenovateBot? (Because clearly their docs are not.) Especially, I'd like to point the bot at a repo locally and just get a list of dependency definitions it found, to see if it discovered everything correctly.

Can anyone recommend a good tutorial on #RenovateBot? (Because clearly their docs are not.) Especially, I'd like to point the bot at a repo locally and just get a list of dependency definitions it found, to see if it discovered everything correctly.

Really grateful for #renovatebot on this project btw.

Really grateful for #renovatebot on this project btw.

Hello fellow #forgejo and #renovateBot users, I need your #help.

I'm currently stuck as my #renovate config can't seem to discover my repos. Anything obvious im doing wrong? Here's a pipeline run example, you can find the config in that repo as well: https://code.cluster.diluz.io/maybeanerd/renovate-runner/actions/runs/35

The renovate token is a token for the user https://code.cluster.diluz.io/renovate-bot and has write&read access to all API scopes.

Die Geschichte vom #rabenyx geht weiter... Von der Kommandozeile zur Webanwendung und viel dabei gelernt! 👉️ https://synyx.de/blog/die-geschichte-vom-rabenyx-teil-2-entwicklung/ #python #flask #gitlabci #renovatebot

Die Geschichte vom #rabenyx geht weiter... Von der Kommandozeile zur Webanwendung und viel dabei gelernt! 👉️ https://synyx.de/blog/die-geschichte-vom-rabenyx-teil-2-entwicklung/ #python #flask #gitlabci #renovatebot

Автоматическое обновление зависимостей в GitLab-проектах с помощью Renovate

Автоматическое обновление зависимостей становится все более важным аспектом в процессах непрерывной интеграции и непрерывной доставки (CI/CD) в сфере разработки программного обеспечения. В статье описана настройка автоматического обновления зависимостей в GitLab-проектах с помощью Renovate.

https://habr.com/ru/companies/magnit/articles/793470/

#обновление #renovate #renovatebot #ci/cd #ci/cd_gitlab #зависимости

Just blogged about some more #renovatebot stuff I've discovered after a months use. https://blog.ostebaronen.dk/2024/02/more-renovate.html

#RenovateBot is so much better than #Github #dependabot to manage your dependencies: merge confidence, automerge, package rule, semversion, grouping... It rocks for a #nofridaydeployment

The most amazing moments with #renovateBot are stuff like entering our own instance of @elk, seeing a post about v0.10.0 being released, and moments later the UI asks to be reloaded due to an update.
It's just magical that the deployment updates in the background effortlessly.

About to merge this #renovatebot PR on a repository that is the root for a dozen subsplit repos. Going to be a fun couple of days to get all changes in. (Limited at two per hour.)

Getting more and more bummed out by #dependabot. The update strategy is set to auto (default by not setting it), and this should have done a widen. Found this while digging into why a whole bunch of packages didn't get 8.2 compatible packages. Time to dig into #renovatebot

Just before🎄Christmas I scanned the #AzureDevOps marketplace for bugs 🐛 and serious security issues 🧨 and found that about 40% of all current extensions contained ☣️ vulnerabilities! And that's when you're on a recent version of each task.

Unfortunately, it's pretty hard to keep all your pipelines up-to-date!

Now you can enable 🔧 #RenovateBot to automatically update your ☣️ pipelines! And it will tell you when to update tasks from all public marketplace extensions too.

https://jessehouwing.net/azure-pipelines-enable-renovatebot/

So cool! #renovatebot just started submitting pull requests for all Azure Pipeline tasks on the marketplace! Sorry for the spam ;). This is all my fault!

https://github.com/jessehouwing/azure-pipelines-gate-condition-editor/issues/10

Keeping my and your #AzureDevOps organizations safe!