tektoncd / tektoncd/pipelines-as-code
Allow using remote tasks in remote pipeline
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 214
- Forks
- 144
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 27
Description
When using a remote pipeline (as described in chapter "Using remote pipeline annotations with Pipelines as Code" in the documentation: https://docs.openshift.com/container-platform/4.11/cicd/pipelines/using-pipelines-as-code.html), it is not possible to reference remote tasks from the remote pipeline.
In other words, when application repository has a .tekton with PipelineRun that uses a remote pipeline from another repository using annotation pipelinesascode.tekton.dev/pipeline - the tasks that the remote pipeline is using have to be available either on the execution cluster or be stored in application repository. What we want is that the remotely accessed pipeline would be able to use tasks from the same remote pipeline repository.
This scenario can be be also represented in this diagram:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with the remote pipeline annotations documentation linked in the issue and reproduce the described PipelineRun scenario. Trace how the remote pipeline and its tasks are resolved; done means a remote pipeline can use tasks from its own remote repository without requiring them on the cluster or in the application repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100