Open dibyom opened 2 years ago
it does appear that there are more than just the getting started that need this attention. most of the pipelines in the examples directory use resources
instead of workspaces. could we make an issue that is just "refactor examples to align with latest pipeline release". once that's done, it may be simpler to break down the Getting Started updates into smaller tasks
could we make an issue that is just "refactor examples to align with latest pipeline release". once that's done, it may be simpler to break down the Getting Started updates into smaller tasks
yeah that sounds like a good idea!
OK, I'm working on the pipeline samples across the entire examples directory now
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen
with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
/remove-lifecycle stale
as per the Triggers WG discussion this issue would be good for Hactoberfest
cc @wlynch
Feature request
The getting started tutorial is fairly old and could use a refresh.
[x] Urgent Remove PipelineResources from the pipeline
[ ] Simplify the Create and execute the ingress and webhook Tasks section
create-ingress
task with a link to the exposing eventlisteners documentation[ ] Simplify the Configure your Cluster section
create-webhook
task[ ] Simplify the Pipeline
[ ] Use more up to date patterns for configuring Triggers
Trigger
resource with inline binding and template instead of a trigger embedded within the EventListener