tektoncd/pipeline

Binary (local) input type

Open

#924 opened on May 29, 2019

View on GitHub
 (11 comments) (5 reactions) (0 assignees)Go (1,943 forks)auto 404
designhelp wantedkind/designkind/questionlifecycle/frozen

Repository metrics

Stars
 (9,013 stars)
PR merge metrics
 (PR metrics pending)

Description

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

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.