Create 2020 roadmap 🛣️ #1999

bobcatfish · 2020-02-04T18:01:37Z

This is a WIP because I would also like additions/changes/feedback specifically from:

The governing board @abayer @vdemeester @kimsterv @dlorenc
Tekton Pipelines OWNERS @afrittoli @dibyom @sbwsg (and @imjasonh but he's on paternity leave so hopefully he ignores this! ❤️ )
Tekton Triggers OWNERS (also if you want to move the triggers section out of this repo and into triggers instead that's 💯 ) @iancoffey @vtereso @ncskier @wlynch

And everyone else of course!!!!

Changes

I have put together a roadmap for 2020, which attempts to represent the
most requested of the features and issues that we've seen so far. I did
this by:

Reviewing the 2019 roadmap
Looking at the oldest and most commented on issues in Tekton Pipelines
and Tekton Triggers

I also added a section on Tekton's mission: this is the mission that
we've been using at Google when talking about Tekton - so this is a
great chance for anyone who is viewing Tekton differently to mention
their mission and vision so we can tweak it. Having more clarity around
what everyone is hoping accomplish with Tekton will make it easier to
make decisions around features, etc.

I have put together a roadmap for 2020, which attempts to represent the most requested of the features and issues that we've seen so far. I did this by: * [Reviewing the 2019 roadmap](https://docs.google.com/document/d/1zClmMJZU63kEDedjxTI99MCK-mXqm-Ym7PBfjMG5tQE/edit) * Looking at the oldest and most commented on issues in Tekton Pipelines and Tekton Triggers I also added a section on Tekton's mission: this is the mission that we've been using at Google when talking about Tekton - so this is a great chance for anyone who is viewing Tekton differently to mention their mission and vision so we can tweak it. Having more clarity around what everyone is hoping accomplish with Tekton will make it easier to make decisions around features, etc.

tekton-robot · 2020-02-04T18:01:44Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign bobcatfish
You can assign the PR to them by writing /assign @bobcatfish in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

vdemeester · 2020-02-04T18:09:01Z

@bobcatfish we should include cli, catalog, dashboard and operator in the ROADMAP I think 😉

tekton-robot · 2020-02-04T18:09:36Z

@bobcatfish: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
pull-tekton-pipeline-build-tests	`9ac5f08`	link	`/test pull-tekton-pipeline-build-tests`

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

vdemeester · 2020-02-04T18:09:36Z

but then, should this ROADMAP be in community or the website (docs) repository ?

afrittoli · 2020-02-04T18:16:24Z

but then, should this ROADMAP be in community or the website (docs) repository ?

We could put it in the community repo, and link to it specific sections from each projects docs.

dibyom

Thanks for writing this up @bobcatfish

I think putting this in the community repo makes sense if we have the roadmaps for all of Tekton (pipelines, triggers, cli, dashboard etc.)

dibyom · 2020-02-04T19:07:25Z

roadmap.md

+
+- [Failure strategies](https:/tektoncd/pipeline/issues/1684)
+- [Conditional execution](https:/tektoncd/pipeline/blob/master/docs/conditions.md)
+ is nearly where we want it, though feedback has indicated this doens't always


typo:
tangent: I think adding FailureStrategies is going to resolve some of the missing bits around conditionals!

i had to read this several times before seeing the typo XD

dibyom · 2020-02-04T19:13:39Z

roadmap.md

+
+* [Improved support for many EventListeners](https:/tektoncd/triggers/issues/370)
+* [Pluggable core interceptors](https:/tektoncd/triggers/issues/271)
+* [Support for expressions in TriggerBindings](https:/tektoncd/triggers/issues/271)


Technically TriggerBindings already support "expressions" -- just the JSONPath kind. The reason for considering CEL was adding support for extensible functions to Bindings..which I guess is my long winded way of saying a better title might be "Support for extensible functions in TriggerBindings" or something 😃

maybe ill change it to something like "increased expression support"

the thing is these "extensible functions" i think are only extensible afaik in that you can build functions into tekton triggers itself, but it's not like users can extend it with functions?

dibyom · 2020-02-04T19:23:36Z

roadmap.md

+* [Performant Triggers](https:/tektoncd/triggers/issues/406)
+* Support for poll-based triggering (e.g. when a repo changes state)
+* Support for additional expression languages
+* Increased traceability (e.g. why did my interceptor reject the event?)


I'd say there are mainly two buckets of use cases that we are working on:

-- one for operator user type use cases (aka the listener part) e.g. how many triggers do I add to my eventListener, how do I scale with many event listeners, how do I expose the EL healthchecks, logs, add/remove custom interceptors etc.

-- end user use cases i.e. trigger definitions: expression languages, built in functions (base64 decoding/ trimming commit SHAs), inline bindings etc.

Okay I've tried to capture this in the newest version but you should feel free to just re-write it!

ghost · 2020-02-04T20:32:21Z

roadmap.md

+
+### Beta and GA
+
+In 2019 we got to the point where we had severl projects built on top of Tekton


nit: severl -> several

making fun of my canadian accent!

ghost · 2020-02-04T20:33:51Z

roadmap.md

+As the project matures, we also require:
+
+1. A website that provides a good landing page for users (tekton.dev)
+1. Solid, high quality on boarding and documentation


nit: on boarding -> onboarding

vdemeester · 2020-02-04T18:22:43Z

roadmap.md

+
+Tekton's mission:
+
+ Be the industry-standard, cloud-native CI/CD platform and ecosystem.


I wonder if this is misleading or not : does tekton aims to be a CI/CD platform on its own or does it aim to provide all the component necessarly to have a CI/CD platform ? (the different, sublte, being that tekton stays un-opiniated)

This is something that can be confusing to end user : do I want to go with straight up Tekton or for something that integrate tekton ?

I wonder if this is misleading or not : does tekton aims to be a CI/CD platform on its own or does it aim to provide all the component necessarly to have a CI/CD platform ? (the different, sublte, being that tekton stays un-opiniated)

How about "platform components" instead of "platform"?

This is something that can be confusing to end user : do I want to go with straight up Tekton or for something that integrate tekton ?

Definitely already confusing! I'm not even sure the answer is clear at the moment. I think that's what I'm trying to get at in the section with the 2 groups of engineers, if you're building a CI/CD system, use Tekton, if not, use something that supports Tekton

bobcatfish · 2020-02-14T19:00:47Z

Okay I've responded to feedback and moved the proposed roadmap over to the community repo at tektoncd/community#77 PTAL! 🎉

Thanks for all the feedback!

tekton-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 4, 2020

googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Feb 4, 2020

tekton-robot requested review from abayer and afrittoli February 4, 2020 18:01

tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Feb 4, 2020

dibyom reviewed Feb 4, 2020

View reviewed changes

ghost reviewed Feb 4, 2020

View reviewed changes

vdemeester reviewed Feb 5, 2020

View reviewed changes

bobcatfish closed this Feb 14, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Create 2020 roadmap 🛣️ #1999

Create 2020 roadmap 🛣️ #1999

bobcatfish commented Feb 4, 2020

tekton-robot commented Feb 4, 2020

vdemeester commented Feb 4, 2020

tekton-robot commented Feb 4, 2020

vdemeester commented Feb 4, 2020

afrittoli commented Feb 4, 2020

dibyom left a comment

dibyom Feb 4, 2020

bobcatfish Feb 14, 2020

dibyom Feb 4, 2020

bobcatfish Feb 14, 2020

bobcatfish Feb 14, 2020

dibyom Feb 4, 2020

bobcatfish Feb 14, 2020

ghost Feb 4, 2020

bobcatfish Feb 14, 2020

ghost Feb 4, 2020

vdemeester Feb 4, 2020

bobcatfish Feb 14, 2020

bobcatfish commented Feb 14, 2020


		### Beta and GA

		In 2019 we got to the point where we had severl projects built on top of Tekton


		Tekton's mission:

		Be the industry-standard, cloud-native CI/CD platform and ecosystem.

Create 2020 roadmap 🛣️ #1999

Create 2020 roadmap 🛣️ #1999

Conversation

bobcatfish commented Feb 4, 2020

Changes

tekton-robot commented Feb 4, 2020

vdemeester commented Feb 4, 2020

tekton-robot commented Feb 4, 2020

vdemeester commented Feb 4, 2020

afrittoli commented Feb 4, 2020

dibyom left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bobcatfish commented Feb 14, 2020