vdemeester

package main

import (
	"context"
	"fmt"
	"log"
	"os"
	"path/filepath"
	"strings"

vdemeester

{"severity":"info","timestamp":"2023-03-28T13:12:45.869Z","logger":"tekton-pipelines-webhook","caller":"webhook/conversion.go:45","message":"Webhook ServeHTTP request=&http.Request{Method:\"POST\", URL:(*url.URL)(0xc0003fdb00), Proto:\"HTTP/1.1\", ProtoMajor:1, ProtoMinor:1, Header:http.Header{\"Accept\":[]string{\"application/json, */*\"}, \"Accept-Encoding\":[]string{\"gzip\"}, \"Content-Length\":[]string{\"24910\"}, \"Content-Type\":[]string{\"application/json\"}, \"User-Agent\":[]string{\"kube-apiserver-admission\"}}, Body:(*http.body)(0xc0006b9ec0), GetBody:(func() (io.ReadCloser, error))(nil), ContentLength:24910, TransferEncoding:[]string(nil), Close:false, Host:\"tekton-pipelines-webhook.tekton-pipelines.svc:443\", Form:url.Values(nil), PostForm:url.Values(nil), MultipartForm:(*multipart.Form)(nil), Trailer:http.Header(nil), RemoteAddr:\"10.244.0.1:9861\", RequestURI:\"/resource-conversion?timeout=30s\", TLS:(*tls.ConnectionState)(0xc000e14420), Cancel:(<-chan struct {})(nil), Response:(*http.Response

vdemeester

Local execution of Pipelines

Agenda

An exploration of how and why running our pipelines locally.

• Why ?

vdemeester

D0
.docker-image://docker.io/library/fedora:latestR
amd64linuxZ

I

Q
/bin/sh
-c

vdemeester

filename: ./examples/taskrun.yaml
INFO[0000] - step: print-date-unix-timestamp            
INFO[0000] - step: print-date-human-readable            
INFO[0000] - step: list-results                         

B.
,docker-image://docker.io/library/bash:latestR
amd64linuxZ

I

vdemeester

apiVersion: appstudio.redhat.io
kind: BuildIt
spec:
  application:
    ref: some-has-app-object
  scan: true
  sign: true
status:
  completionTime: "2020-05-04T02:19:14Z"
  conditions:

vdemeester

apiVersion: tekton.dev/v1alpha1
kind: Task
metadata:
  name: golang-build
spec:
  inputs:
    params:
    - name: package
      description: base package to build in
    - name: packages

vdemeester

Knative Build deprecation in favor of Tekton Pipelines Steering Committee proposal

Author: Vincent Demeester vdemeest@redhat.com Date: June 6 2019

Objective

Propose to mark knative/build as deprecated and drive user to the Tekton project as their building engine. This doc should be used as a forum for external comment and questions, to resolve any concerns before the Steering Committee decides whether to adopt the proposal.

Background

vdemeester

apiVersion: v1
kind: Namespace
metadata:
  name: tekton-pipelines

---
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
  name: tekton-pipelines

vdemeester

apiVersion: v1
kind: Namespace
metadata:
  name: tekton-pipelines

---
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
  name: tekton-pipelines