[BUG] Docker :release tag procedure and CI config
#3953
Assignees
Labels
bug
issue confirmed as bug
discuss
ask for feedback
docker
issues related to our container images
enhancement
new features, suggestions, etc.
needs documentation
Signals issues or PRs that will require an update to the documentation repo
Comments
duncdrum
added
bug
duncdrum
added a commit
to duncdrum/exist
that referenced
this issue
Jan 6, 2025
keep :latest and :release tags aligned add dev:6 tag for snapshots from develop-6.x.x see eXist-db#3953
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The release of
5.3.0has revealed a misconfiguration of the docker deploy CI config. It expects a PR against themasterbranch, but it only gets a push event.The
:releaseimages are published regardless as part of the local build of the release manager. Don't ask me how I managed to configure the plugin to do that, i vaguely recall doing this on purpose. given the long cadence of releases between5.2.0and5.3.0i suggest reinstating the scheduled rebuilds of the master branch for thereleasetag so that:releaseimages benefit from periodic jvm updates, latest version of autodeploy apps OOTB. etc. This would increase container security, reinstate previous behaviour where users might have been caught unaware of changes, and increase quality of live for maintainers of our CI, since:releaseimages will after a delay ship with the e.g. the latest templating lib, in case of updates to the lib after the official release.see #3914
The text was updated successfully, but these errors were encountered: