-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add step composition to Tasks #3807
Commits on Mar 4, 2021
-
so that we can reuse steps from tekton catalog or any git repository or OCI bundle easily to promote reuse and avoid copy and paste
Configuration menu - View commit details
-
Copy full SHA for 8cce40e - Browse repository at this point
Copy the full SHA 8cce40eView commit details
Commits on Mar 5, 2021
-
fix: added more unit tests for Task/TaskRun/Pipeline
so that we can reuse steps in all tekton resources
Configuration menu - View commit details
-
Copy full SHA for bf22448 - Browse repository at this point
Copy the full SHA bf22448View commit details -
fix: lets add support for reusing Task resources in k8s
and align with the TaskRef struct in tekton. also lets rename the git URI to `git` instead of `path` so its more explicit and fits more cleanly with the `TaskRef`
Configuration menu - View commit details
-
Copy full SHA for 914aebe - Browse repository at this point
Copy the full SHA 914aebeView commit details -
Configuration menu - View commit details
-
Copy full SHA for feef5ee - Browse repository at this point
Copy the full SHA feef5eeView commit details -
as it adds complexity and no longer seems terribly useful when uses: can be a ref/bundle/git
Configuration menu - View commit details
-
Copy full SHA for ba2367e - Browse repository at this point
Copy the full SHA ba2367eView commit details -
fix: lets avoid the Uses.server property
so that a single string, `git` can be used like `bundle` to reference versioned files in any git repository using `kpt` style URIs. Improved support for non-github servers Given its a single simple string URI, we could also reuse `git` on `TaskRef` some day to reference Tasks on Pipelines using git.
Configuration menu - View commit details
-
Copy full SHA for 81ea24f - Browse repository at this point
Copy the full SHA 81ea24fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 8ad1170 - Browse repository at this point
Copy the full SHA 8ad1170View commit details -
lets move the 'git' property into the TaskRef
we can then simplify `Uses` to just be an optional `step` name to indicate whether a single step is being used or all of the steps. We can then look to reuse the git resource loading for `Pipeline.taskRef` too like we do for `bundle`
Configuration menu - View commit details
-
Copy full SHA for 7ae20d1 - Browse repository at this point
Copy the full SHA 7ae20d1View commit details
Commits on Mar 6, 2021
-
lets share the git code with Pipeline.taskRef
so we can load Tasks from git too
Configuration menu - View commit details
-
Copy full SHA for 39ee39e - Browse repository at this point
Copy the full SHA 39ee39eView commit details -
lets avoid using TaskRef directly inside the Uses struct
as it leads to the confusing 'name' property; lets use 'task' instead then its more clear. It also helps us have better comments to properly describe when and why you would use the 'task' property when using a bundle or git
Configuration menu - View commit details
-
Copy full SHA for ee8ee3f - Browse repository at this point
Copy the full SHA ee8ee3fView commit details