Support remote resolution in `pipeline start` and `task start` commands
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 461
- Forks
- 277
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 95
Description
Feature request
Support remote resolution in pipeline start and task start commands
Use case
Start a pipeline or task through remote resolution.
For instance, start a release pipeline using the version of the pipeline associated with the git sha being released.
UI Example
To be consistent with the workspace design, it could be something like:
pipeline start release --remote resolver=git,url=https://github.com/tektoncd/pipeline.git,revision=main, pathInRepo=tekton/pipeline-release.yaml
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
Start by locating the implementations of the pipeline start and task start commands and the existing workspace remote-resolution behavior referenced in the issue. Determine how the resolver syntax should be shared by both commands; done means each command can start a resource resolved from a remote Git repository using the proposed options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100