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

Task Result path should be available as a variable #1977

Closed
ghost opened this issue Jan 29, 2020 · 2 comments
Closed

Task Result path should be available as a variable #1977

ghost opened this issue Jan 29, 2020 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. maybe-next-milestone For consideration when planning the next milestone

Comments

@ghost
Copy link

ghost commented Jan 29, 2020

Expected Behavior

The path for a task result should be available as a variable that can be interpolated into scripts. Example YAML we'd like to support:

  # Task Spec
  results:
    - name: current-date-unix-timestamp
      description: The date in unix timestamp format.
  steps:
    - name: print-date-unix-timestamp
      image: bash:latest
      script: date +%s | tee $(results.current-date-unix-timestamp.path)

In the above example we'd like $(results.current-date-unix-timestamp.path) to resolve to /tekton/results/current-date-unix-timestamp.

Actual Behavior

At the moment the user has to hard-code the task result path into their Task's script. In other words, if a user wants their Step Container to emit a task result then they need to physically write out /tekton/results/result-name in their code.

Additional Info

Suggested by @afrittoli here.

@ghost ghost added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 29, 2020
@ghost ghost added the maybe-next-milestone For consideration when planning the next milestone label Jan 29, 2020
@othomann
Copy link
Contributor

@sbwsg #2018 has been merged. So this issue can be closed. I cannot assign it to me.

@ghost
Copy link
Author

ghost commented Feb 11, 2020

👍 thanks @othomann !

@ghost ghost closed this as completed Feb 11, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. maybe-next-milestone For consideration when planning the next milestone
Projects
None yet
Development

No branches or pull requests

1 participant