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
# adding a hadolint ignore for SC2215, due to https://github.com/hadolint/hadolint/issues/980
23
-
# hadolint ignore=SC2215
24
-
RUN --mount=type=cache,id=maven-${PRODUCT},target=/root/.m2/repository <<EOF
25
-
cd "$(/stackable/patchable --images-repo-root=src checkout trino ${PRODUCT})"
26
-
27
-
# Create snapshot of the source code including custom patches
28
-
tar -czf /stackable/trino-${PRODUCT}-src.tar.gz .
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
# adding a hadolint ignore for SC2215, due to https://github.com/hadolint/hadolint/issues/980
15
+
# hadolint ignore=SC2215
16
+
RUN --mount=type=cache,id=maven-${PRODUCT},target=/root/.m2/repository <<EOF
17
+
cd "$(/stackable/patchable --images-repo-root=src checkout trino/trino ${PRODUCT})"
18
+
19
+
NEW_VERSION="${PRODUCT}-stackable${RELEASE}"
20
+
21
+
mvn versions:set -DnewVersion=$NEW_VERSION
22
+
23
+
# Create snapshot of the source code including custom patches
24
+
tar -czf /stackable/trino-${NEW_VERSION}-src.tar.gz .
25
+
26
+
# Trino is using something (git-commit-id-plugin in the past, maybe something else now) that is
27
+
# reading the Git history and searches for a tag to pull the version from. It sounds weird to me
28
+
# why someone would do that over just picking the version from the pom.xml, but they propably
29
+
# have their reasons. See e.g. https://github.com/trinodb/trino/discussions/18963.
30
+
# So we fake it till we make it and create a Git repo and the correct tag. The trino-operator
31
+
# smoke test checks that "select version()" is working.
32
+
# 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