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

Folders for output resource not created in multiple scenario #1630

Closed
vincent-pli opened this issue Nov 27, 2019 · 2 comments
Closed

Folders for output resource not created in multiple scenario #1630

vincent-pli opened this issue Nov 27, 2019 · 2 comments
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.

Comments

@vincent-pli
Copy link
Member

I have a task with more than one output resource, like this:

apiVersion: tekton.dev/v1alpha1
kind: Task
metadata:
  name: build-push
spec:
  outputs:
    resources:
    - name: builtImage
      type: image
    - name: builtImage1
      type: image
  steps:
  - name: build-and-push
    image: docker
    args: ["touch", "$(outputs.resources.builtImage.path)/README.md"]
  - name: build-and-push-1
    image: docker
    args: ["touch", "$(outputs.resources.builtImage1.path)/README.md"]

Base on the document, folders named: /workspace/output/resource_name/ should be created.

The fact is the /workspace/output/builtImage is created and step: build-and-push is success but the step: build-and-push-1 is failed, since /workspace/output/builtImage1 is not existed, found logs: touch: /workspace/output/builtImage1/README.md: No such file or directory

Expected Behavior

Taskrun success

Actual Behavior

Taskrun failed

Steps to Reproduce the Problem

Additional Info

@vdemeester
Copy link
Member

/kind bug

@tekton-robot tekton-robot added the kind/bug Categorizes issue or PR as related to a bug. label Nov 27, 2019
@bobcatfish bobcatfish added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Nov 27, 2019
@afrittoli
Copy link
Member

I wonder if this one and #1632 are related?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

5 participants