-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-build image on new mod versions #122
Comments
As
This repository here is used as a GitHub Action within icingaweb2: https://github.com/Icinga/icingaweb2/blob/main/.github/workflows/docker.yml One easy fix would be to include a GitHub Action Job similar to those in icingaweb2 for |
Good idea! IMAO we should let this happen weekly. People on the latest tag expect and want the latest stuff. In case of breaking changes in mods users even have multiple options:
CC @lippserd |
I'd be interested in testing your new ini-parsing PR in a :latest tag as well 🙂 |
TODO
|
We also would like a new release with the latest icingadb(-web) version :-). |
I use icinga/icingaweb2 as base for our install.
Unfortunately the image only gets build when there is a new icingaweb release. As the release of icingaweb is not increased when major plugins are updated (e.g. icingadbweb) I end up manually bind-mounting more current plugin releases into the container.
There is the main tag which appears to be build daily, but I didn't find any CI chain for this.
Is there any chance of building the icingaweb2 image more often or even linking the github actions once an included plugin gets updated?
The text was updated successfully, but these errors were encountered: