You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: trino/Dockerfile
+14-1Lines changed: 14 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,20 @@ cd "$(/stackable/patchable --images-repo-root=src checkout trino ${PRODUCT})"
27
27
# Create snapshot of the source code including custom patches
28
28
tar -czf /stackable/trino-${PRODUCT}-src.tar.gz .
29
29
30
+
# Trino is using something (git-commit-id-plugin in the past, maybe something else now) that is
31
+
# reading the Git history and searches for a tag to pull the version from. It sounds weird to me
32
+
# why someone would do that over just picking the version from the pom.xml, but they propably
33
+
# have their reasons. See e.g. https://github.com/trinodb/trino/discussions/18963.
34
+
# So we fake it till we make it and create a Git repo and the correct tag. The trino-operator
35
+
# smoke test checks that "select version()" is working.
36
+
# Also, we need to initialize a new Git repo because `git-commit-id-maven-plugin` has a problem with worktrees, see https://github.com/git-commit-id/git-commit-id-maven-plugin/issues/215
0 commit comments