Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TEP-0063: Workspace Dependencies #413

Merged
merged 1 commit into from
May 10, 2021

Commits on May 10, 2021

  1. TEP-0063: Workspace Dependencies

    In this PR, we discuss the motivation, goals, non-goals and requirements
    for `Workspace` dependencies so that we can align on the problem before
    exploring the proposal and alternatives later
    
    `Tasks` can have either resource dependencies or ordering dependencies
    between them. Resource dependencies are based on `Results` and
    `Workspaces`, while ordering dependencies are defined using `runAfter`
    to sequence `Tasks`.
    
    Today, users cannot specify resource dependencies based on `Workspaces`,
    that is, a `Task` should execute and use a given `Workspace` before
    another `Task` executes and uses the same `Workspace`. We need to
    provide a way for users to specify resource dependencies based on
    `Workspaces` to ensure that failure and skipping strategies for
    common CI/CD use cases work and users don't get unexpected `Pipeline`
    failures when we roll out those features.
    
    Failure and skipping strategies:
    - [TEP-0059: Skip Guarded Task Only](https://github.com/tektoncd/community/blob/main/teps/0059-skip-guarded-task-only.md)
    - [TEP-0050: Ignore Task Failures](https://github.com/tektoncd/community/blob/main/teps/0050-ignore-task-failures.md)
    
    Issue: tektoncd/pipeline#3109
    jerop committed May 10, 2021
    Configuration menu
    Copy the full SHA
    6474293 View commit details
    Browse the repository at this point in the history