mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 16:25:55 +03:00
[GH-ISSUE #613] Improved Image Versioning and Release Cycle #227
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#227
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @RedlineTriad on GitHub (Jun 23, 2023).
Original GitHub issue: https://github.com/lldap/lldap/issues/613
https://hub.docker.com/r/nitnelave/lldap/tags
Currently only the latest images seem to be frequently updated, but it would be nice to have daily, or per PR images.
I use renovate bot to automatically update images, but when using latest that doesn't work.
But if I were to use the named images I would be months behind in the development cycle, which would be annoying.
Grafana images have very nice versioning as an example:
https://hub.docker.com/r/grafana/grafana/tags
Also, hello from hackernews :D
@martadinata666 commented on GitHub (Jun 24, 2023):
My 2 cents here, why do we need daily images? or even per PR image cluttering up the tags page. Can it use
:maintag? If it can, then imo should take the issue to renovate as grafana:mainwork the same as lldap:latest, I assume it can't as the renovate docs only accepting semver? The only exception isubuntu:somethingordebian:something, it's just weird renovate don't want to support it for other images.Then lastly yes, lldap on a slow pace as it a community project that time is not our friend.
Thanks for the input anyway ☕
@RedlineTriad commented on GitHub (Jun 24, 2023):
@martadinata666
If I use the main tag I don't know which image is actually deployed, I don't care much about semver but I do care about determinism and having software versions in git with rollback possibilities.
Or even with a bug report I can't say I just use latest, and using a months old version when reporting bugs is also bad. So the best thing I can do is go on the server manually and get the digest of the image, and even with that there might be no way to map it back to a git commit.
I would just like versioned builds that are as up to date as possible, what those versions are is not that important.