如何在Tekton Hub的Maven Task中实现Maven依赖缓存？

核心实现逻辑是通过持久化存储PVC挂载Maven本地仓库目录，让多次PipelineRun复用已下载的依赖包，具体操作步骤如下：

1. 创建Maven缓存专用PersistentVolumeClaim #

先创建单独的PVC用于存储所有Maven依赖包，避免和源码存储混用，配置示例：

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: maven-cache-pvc
spec:
  accessModes:
    - ReadWriteOnce # 多节点集群可改为ReadWriteMany
  resources:
    requests:
      storage: 10Gi # 可根据实际依赖总量调整大小

使用kubectl apply -f maven-cache-pvc.yaml完成创建。

2. 调整Pipeline定义新增缓存Workspace #

修改原有Pipeline配置，新增Maven缓存对应的workspace并绑定到Maven Task：

apiVersion: tekton.dev/v1beta1
kind: Pipeline
metadata:
  name: buildpacks-test-pipeline
spec:
  params:
    - name: SOURCE_URL
      type: string
      description: A git repo url where the source code resides.
    - name: SOURCE_REVISION
      description: The branch, tag or SHA to checkout.
      default: ""

  workspaces:
    - name: maven-settings
    - name: source-workspace
    - name: maven-repo # 新增Maven缓存workspace
  tasks:
    - name: fetch-repository
      taskRef:
        name: git-clone
      workspaces:
        - name: output
          workspace: source-workspace
      params:
        - name: url
          value: "$(params.SOURCE_URL)"
        - name: revision
          value: "$(params.SOURCE_REVISION)"
        - name: subdirectory
          value: ""
        - name: deleteExisting
          value: "true"
    - name: maven
      taskRef:
        name: maven
      runAfter:
        - fetch-repository
      params:
        - name: GOALS
          value:
            - package
        # 可选：显式指定Maven本地仓库路径，避免默认路径适配问题
        # - name: MAVEN_OPTS
        #   value: "-Dmaven.repo.local=$(workspaces.maven-repo.path)"
      workspaces:
        - name: source
          workspace: source-workspace
        - name: maven-settings
          workspace: maven-settings
        - name: maven-repo # 绑定缓存workspace到Maven Task
          workspace: maven-repo

使用kubectl apply -f pipeline.yaml更新Pipeline配置。

3. 调整PipelineRun绑定缓存PVC #

修改PipelineRun配置，将新增的maven-repo workspace绑定到第一步创建的PVC：

apiVersion: tekton.dev/v1beta1
kind: PipelineRun
metadata:
  generateName: buildpacks-test-pipeline-run-
spec:
  pipelineRef:
    name: buildpacks-test-pipeline
  workspaces:
    - name: maven-settings
      emptyDir: {}
    - name: source-workspace
      subPath: source
      persistentVolumeClaim:
        claimName: source-pvc
    - name: maven-repo # 绑定Maven缓存PVC
      persistentVolumeClaim:
        claimName: maven-cache-pvc
  params:
    - name: SOURCE_URL
      value: https://gitlab.com/jonashackt/microservice-api-spring-boot
    - name: SOURCE_REVISION
      value: 3c4131f8566ef157244881bacc474543ef96755d

配置完成后重新启动PipelineRun，第二次及以后的构建就会复用已下载到maven-cache-pvc中的依赖包，无需重复下载。

可选优化 #

• 如果集群为多节点架构，将maven-cache-pvc的accessModes改为ReadWriteMany，支持多节点并发构建复用缓存
• 可定期执行mvn dependency:purge-local-repository清理缓存中过时的依赖包，避免PVC存储空间占用过高

内容的提问来源于stack exchange，提问作者jonashackt