how do I set pipelinerun wait for the previous pipelinerun execution to complete

[dgsfor]

I want to set pipelinerun in serial, because the task in pipeline use the same pvc

[Yongxuanzhang]

Hi, could you elaborate your use cases? Why not put the tasks in the same pipeline if they have dependency?

[dibyom]

If I am reading this correctly, you have multiple runs of the same pipeline but they all need to share a single PVC that can only be mounted to one pod at a time. In that case, tektoncd/community#818 might be what you need

[dgsfor]

@dibyom yes,I use git-clone and build code task in pipeline, but the git-clone task will clean the pvc workspace, and the build code task will have some error.

[Yongxuanzhang]

Wonder if pipeline in pipeline is able to address this issue?
https://github.com/tektoncd/community/blob/fc1dd1065a7325cee6b3df1b36f6bedb316d7d8d/teps/0056-pipelines-in-pipelines.md#tep-0056-pipelines-in-pipelines

[dgsfor]

In fact, there are two points to this problem：
1.How to control concurrency
2.How to solve multiple pipelineruns using the same pvc problem

Regarding the first point, it has not yet been resolved and needs to be seen in the subsequent update iterations。

Regarding the second point, I have implemented two solutions so far:
1.When creating a pipelinerun, use volumeClaimTemplate to create random PVCs

apiVersion: tekton.dev/v1beta1
kind: PipelineRun
metadata:
  generateName: eve-php-pre-volumeclaimtemplate-
  namespace: tekton-run
spec:
  workspaces:
    - name: git-clone-workspace-random
      volumeClaimTemplate:
        spec:
          accessModes:
            - ReadWriteOnce
          resources:
            requests:
              storage: 1Gi

2.If you use TriggerTemplate, then you can specify in resourcetemplates that workspace uses pvc's subPath capability,different directories can be created by $(uid)

apiVersion: triggers.tekton.dev/v1alpha1
kind: TriggerTemplate
metadata:
  name: trigger-template-eve-php-pre
  namespace: tekton-run
spec:
  params:
    - name: user-username
  resourcetemplates:
    - apiVersion: tekton.dev/v1beta1
      kind: PipelineRun
      metadata:
        generateName: eve-php-pre-pipelinerun-
        namespace: tekton-run
      spec:
        workspaces:
          - name: git-clone-workspace
            persistentVolumeClaim:
              claimName: pvc-tekton
            subPath: pvc-$(uid)

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.