tektoncd/pipeline

Binary (local) input type

Offen

#924 geöffnet am 29.05.2019

 (11 Kommentare) (5 Reaktionen) (0 zugewiesene Personen)Go (1.943 Forks)auto 404
designhelp wantedkind/designkind/questionlifecycle/frozen

Repository-Metriken

Stars
 (9.013 Sterne)
PR-Merge-Metriken
 (Durchschn. Merge 9T 3h) (137 gemergte PRs in 30 T)

Beschreibung

Openshift builds have a really neat concept of Binary (local) sources. Essentially, it gives you an API to stream binary contents into a build from anywhere (including the local file system).

This opens the door for nice FaaS-style user-experiences, where the user might want to do something like cli create my-large-packaged-nodejs-function.zip, then expect this to be build into a container image and ultimately that image then being pushed to run somewhere (for example Knative Serving).

This flow would be possibly without requiring the user to push this code somewhere and without the user having to install software to build and manage images.

Would that be something that Tekton could support?

Contributor Guide