Christie Warwick (Wilson)

Results 19 issues of Christie Warwick (Wilson)

**Actual behavior** Tekton is using Kaniko to build a Docker image from alpine and recently the builds started failing. _TL;DR_ The alpine:3.12 image has /var/run aliased to /run. When running...

kind/bug
work-around-available
priority/p3
area/behavior

# Expected Behavior If I create a Task which claims to emit a result, but it doesn't, the TaskRun should fail, i.e. I should be able to rely on the...

kind/bug
lifecycle/frozen
priority/important-soon

It would be great to get more detail in the definition of ["build service"](https://slsa.dev/spec/v0.1/requirements#build-service) if possible. It seems like a hard phrase to pin down - and seems to boil...

clarification
slsa 2

[The SLSA requirements](https://slsa.dev/spec/v0.1/requirements) refer in a few places to the term `builder`, however that phrase is not (yet) defined [in the terminology](https://slsa.dev/spec/v0.1/terminology). It would be helpful to have this term...

clarification
slsa 1
maybe-1.0

Another phrase which occurs a few times [in the SLSA requirements](https://slsa.dev/spec/v0.1/requirements) but is not clearly defined (or I haven't found the definition!) is **trusted control plane**. It would be very...

clarification
slsa 3

# Expected Behavior As a user of Tasks in the catalog, when I use Task (or Pipeline) and I specify a specific version X, I should be confident that the...

lifecycle/frozen

The proposals we've had so far around the catalog have centered around supporting Tasks. Though we've always known we wanted to support more types, we haven't thought through how to...

kind/feature
lifecycle/frozen

(moved from https://github.com/tektoncd/pipeline/issues/1489 by @evgf) # Expected Behavior It should be possible to trigger on any change to the state of a repo (i.e. poll based). (I'm assuming we're talking...

kind/feature
lifecycle/frozen
area/roadmap

TriggerTemplates are very generic and can (theoretically) be used to create anything. We initially made them very generic on purpose b/c this felt like a better design: less coupling =...

lifecycle/frozen

# Expected Behavior In our recent working group meeting, @mnuttall described his use case where he wants to have triggering for many repos, where each needs to have different eventlistener...

kind/feature
lifecycle/frozen
area/roadmap