Provide version tags on hub.docker.com about syslog-ng-docker HOT 6 CLOSED

Hello,
this is an old dept from us. Unfortunately there are some manual steps between the GitHub release (which is automated) and the Docker image build (which is also automated).

I tagged the latest image now with the 3.19.1 version, and added this step to our internal release guide, but currently I can not ensure this will happen in the future. (In an automated way.) I will do my best.

Br,
Laci

from syslog-ng-docker.

https://hub.docker.com/r/balabit/syslog-ng/tags

resolved & close?

from syslog-ng-docker.

Tags are still pushed manually, I think we should keep this issue open until we find a way to automate this with OBS, or just document as a step in the release process.

from syslog-ng-docker.

would it be possible to merge the dockerbuild into the main repo. Could we not have travis build docker "latest" and version tags when a release is cut?

from syslog-ng-docker.

@rfaircloth-splunk I am afraid the situation is a little more complex than that. The main repository is responsible for providing a release tarball. But syslog-ng in the images are not built from source, but installed as debian packages from the unofficial repository hosted at build.opensuse.org (OBS). So the trigger point is when the packages are generated in OBS. What would resolve this if the packages in OBS could be generated automatically, and OBS could trigger the docker image generation once the packages are available. But OBS is a very complex topic on its own. So for now we are doing all these steps manually.

from syslog-ng-docker.

Updated: https://github.com/syslog-ng/syslog-ng/releases/tag/syslog-ng-3.30.1

from syslog-ng-docker.