main
  1<!DOCTYPE html>
  2<html lang="en">
  3<head>
  4<!-- Sep 03, 2024 -->
  5<meta charset="utf-8" />
  6<meta name="viewport" content="width=device-width, initial-scale=1" />
  7<title>Tekton</title>
  8<meta name="author" content="Vincent Demeester" />
  9<meta name="generator" content="Org Mode" />
 10<link rel='icon' type='image/x-icon' href='/images/favicon.ico'/>
 11<meta name='viewport' content='width=device-width, initial-scale=1'>
 12<link rel='stylesheet' href='/css/new.css' type='text/css'/>
 13<link rel='stylesheet' href='/css/syntax.css' type='text/css'/>
 14<link href='/index.xml' rel='alternate' type='application/rss+xml' title='Vincent Demeester' />
 15</head>
 16<body>
 17<main id="content" class="content">
 18<header>
 19<h1 class="title">Tekton</h1>
 20</header><section id="outline-container-What%20is%20Tektoncd%20%3F" class="outline-2">
 21<h2 id="What%20is%20Tektoncd%20%3F">What is Tektoncd ?</h2>
 22<div class="outline-text-2" id="text-What%20is%20Tektoncd%20%3F">
 23<div class='drawer logbook'>
 24<h6>Logbook</h6>
 25nil</div>
 26
 27
 28<figure id="org0aac350">
 29<img src="./images/tekton/tekton-horizontal-color.png" alt="tekton-horizontal-color.png" width="400/600px">
 30
 31</figure>
 32
 33<blockquote>
 34<p>
 35The Tekton Pipelines project provides <a href="kubernetes.html">Kubernetes</a>-style resources for declaring <a href="continuous_integration.html">CI</a>/<a href="continuous_deployment.html">CD</a>-style pipelines.
 36</p>
 37</blockquote>
 38
 39<ul class="org-ul">
 40<li>Started as an experiment from <a href="knative.html">knative</a> to define more advance build use cases that
 41<a href="https://github.com/knative/build/"><code>knative/build</code></a> was able to.</li>
 42<li>Is now it&rsquo;s own <a href="https://tekton.dev">project</a> and <a href="https://github.com/tetkon">GitHub organization</a>.</li>
 43</ul>
 44
 45<p>
 46It can be deployed in <a href="openshift.html">OpenShift</a> either using the upstream releases or with <a href="openshift_pipeline.html">OpenShift
 47Pipeline</a>.
 48</p>
 49
 50<p>
 51As it is running in <a href="kubernetes.html">Kubernetes</a>, everything runs into <a href="containers.html">containers</a>.
 52</p>
 53</div>
 54</section>
 55<section id="outline-container-Guides" class="outline-2">
 56<h2 id="Guides"><span class="todo TODO">TODO</span> Guides</h2>
 57<div class="outline-text-2" id="text-Guides">
 58</div>
 59<div id="outline-container-%5B%5Bfile%3Atekton-migrating-from-jenkins.org%5D%5BMigrating%20from%20Jenkins%20to%20Tekton%5D%5D" class="outline-3">
 60<h3 id="%5B%5Bfile%3Atekton-migrating-from-jenkins.org%5D%5BMigrating%20from%20Jenkins%20to%20Tekton%5D%5D"><span class="todo TODO">TODO</span> <a href="tekton-migrating-from-jenkins.html">Migrating from Jenkins to Tekton</a></h3>
 61<div class="outline-text-3" id="text-%5B%5Bfile%3Atekton-migrating-from-jenkins.org%5D%5BMigrating%20from%20Jenkins%20to%20Tekton%5D%5D">
 62<p>
 63The gist of this guide is to help you migrate from Jenkins (using <code>Jenkinsfile</code>, or not) to
 64Tekton pipelines.
 65</p>
 66</div>
 67</div>
 68<div id="outline-container-Efficient%20Tekton%20Pipelines" class="outline-3">
 69<h3 id="Efficient%20Tekton%20Pipelines"><span class="todo TODO">TODO</span> Efficient Tekton Pipelines</h3>
 70</div>
 71</section>
 72<section id="outline-container-Contributing" class="outline-2">
 73<h2 id="Contributing">Contributing</h2>
 74<div class="outline-text-2" id="text-Contributing">
 75<ul class="org-ul">
 76<li><a href="tekton_dev.html">Tekton development environment</a> is a good <i>getting started</i> article.</li>
 77<li><a href="https://github.com/tektoncd/community/blob/master/teps/README.md">Tekton Enhancement proposals (TEPs)</a> are a good way to see what and how are the features
 78discuss in the tekton community.</li>
 79</ul>
 80</div>
 81<div id="outline-container-Design%20Docs" class="outline-3">
 82<h3 id="Design%20Docs">Design Docs</h3>
 83<div class="outline-text-3" id="text-Design%20Docs">
 84<p>
 85Let&rsquo;s list some interesting design docs I worked on (or reviewed).
 86</p>
 87
 88<ul class="org-ul">
 89<li><a href="https://docs.google.com/document/d/10nQSeIse7Ld4fLg4lhfgUmNKtewfaFNET3zlMdRnBuQ/edit#heading=h.nz0qjg4cmzp0">Tekton Custom Tasks</a></li>
 90</ul>
 91</div>
 92</div>
 93<div id="outline-container-TEPs%20%3A%20Tekton%20Enhancement%20Proposals" class="outline-3">
 94<h3 id="TEPs%20%3A%20Tekton%20Enhancement%20Proposals">TEPs : Tekton Enhancement Proposals</h3>
 95<div class="outline-text-3" id="text-TEPs%20%3A%20Tekton%20Enhancement%20Proposals">
 96<p>
 97<span class="timestamp-wrapper"><span class="timestamp">[2020-06-17 Wed] </span></span> TEP, or Tekton Enhancement Proposal is a new process to to propose,
 98communicate and coordinate on new efforts for the Tekton project. You can read the full
 99details of the project in <a href="https://github.com/tektoncd/community/blob/master/teps/0001-tekton-enhancement-proposal-process.md">TEP-1</a>.
100</p>
101
102<blockquote>
103<p>
104A standardized development process for Tekton is proposed in order to
105</p>
106
107<ul class="org-ul">
108<li>provide a common structure and clear checkpoints for proposing changes to Tekton</li>
109<li>ensure that the motivation for a change is clear</li>
110<li>allow for the enumeration stability milestones and stability graduation criteria</li>
111<li>persist project information in a Version Control System (VCS) for future Tekton users
112and contributors</li>
113<li>support the creation of high value user facing information such as:
114<ul class="org-ul">
115<li>motivation for impactful user facing changes</li>
116<li>an overall project development roadmap</li>
117</ul></li>
118<li>ensure community participants are successfully able to drive changes to completion
119across one or more releases while stakeholders are adequately represented throughout the
120process</li>
121</ul>
122
123<p>
124<b>This process is supported by a unit of work called a Tekton Enhancement Proposal (TEP)</b>. A
125TEP attempts to combine aspects of the following:
126</p>
127
128<ul class="org-ul">
129<li>feature, and effort tracking document</li>
130<li>a product requirements document</li>
131<li>design document</li>
132</ul>
133
134<p>
135into one file which is created incrementally in collaboration with one or more <a href="https://github.com/tektoncd/community/blob/master/working-groups.md">Working
136Groups (WGs)</a>.
137</p>
138
139<p>
140This process does not block authors from doing early design docs using any means. It does
141not block authors from sharing those design docs with the community (during Working
142groups, on Slack, GitHub, ….
143</p>
144
145<p>
146This process acts as a requirement when a design docs is ready to be implemented or
147integrated in the tektoncd projects. In other words, a change that impact other tektoncd
148projects or users cannot be merged if there is no TEP associated with it.
149</p>
150
151<p>
152This TEP process is related to
153</p>
154
155<p>
156the generation of an architectural roadmap
157the fact that the what constitutes a feature is still undefined
158issue management
159the difference between an accepted design and a proposal
160the organization of design proposals
161</p>
162
163<p>
164This proposal attempts to place these concerns within a general framework.
165</p>
166</blockquote>
167
168<p>
169The TEPs should be publish at <a href="https://teps.tekton.dev">https://teps.tekton.dev</a> at some point.
170</p>
171</div>
172</div>
173</section>
174<section id="outline-container-Links" class="outline-2">
175<h2 id="Links">Links</h2>
176<div class="outline-text-2" id="text-Links">
177</div>
178<div id="outline-container-%5B%5Bhttps%3A%2F%2Flewo.abesis.fr%2Fposts%2F2019-09-30-tekton-pipelines-the-nix-way.html%5D%5BLewo%20-%20Tekton%20Pipelines%20-%20the%20Nix%20way%5D%5D" class="outline-3">
179<h3 id="%5B%5Bhttps%3A%2F%2Flewo.abesis.fr%2Fposts%2F2019-09-30-tekton-pipelines-the-nix-way.html%5D%5BLewo%20-%20Tekton%20Pipelines%20-%20the%20Nix%20way%5D%5D"><span class="todo TODO">TODO</span> <a href="https://lewo.abesis.fr/posts/2019-09-30-tekton-pipelines-the-nix-way.html">Lewo - Tekton Pipelines - the Nix way</a></h3>
180<div class="outline-text-3" id="text-%5B%5Bhttps%3A%2F%2Flewo.abesis.fr%2Fposts%2F2019-09-30-tekton-pipelines-the-nix-way.html%5D%5BLewo%20-%20Tekton%20Pipelines%20-%20the%20Nix%20way%5D%5D">
181<p>
182<span class="timestamp-wrapper"><span class="timestamp">[2019-10-09 Wed 17:05]</span></span>
183</p>
184</div>
185</div>
186<div id="outline-container-%5B%5Bhttps%3A%2F%2Fmustafaakin.dev%2Fposts%2F2020-04-26-using-jsonnet-to-generate-dynamic-tekton-pipelines-in-kubernetes%2F%5D%5BUsing%20Jsonnet%20to%20Generate%20Dynamic%20Tekton%20Pipelines%20in%20Kubernetes%20%C2%B7%20Mustafa%20Ak%C4%B1n%5D%5D" class="outline-3">
187<h3 id="%5B%5Bhttps%3A%2F%2Fmustafaakin.dev%2Fposts%2F2020-04-26-using-jsonnet-to-generate-dynamic-tekton-pipelines-in-kubernetes%2F%5D%5BUsing%20Jsonnet%20to%20Generate%20Dynamic%20Tekton%20Pipelines%20in%20Kubernetes%20%C2%B7%20Mustafa%20Ak%C4%B1n%5D%5D"><span class="todo TODO">TODO</span> <a href="https://mustafaakin.dev/posts/2020-04-26-using-jsonnet-to-generate-dynamic-tekton-pipelines-in-kubernetes/">Using Jsonnet to Generate Dynamic Tekton Pipelines in Kubernetes · Mustafa Akın</a>&#xa0;&#xa0;&#xa0;<span class="tag"><span class="kubernetes">kubernetes</span>&#xa0;<span class="tetkon">tetkon</span></span></h3>
188<div class="outline-text-3" id="text-%5B%5Bhttps%3A%2F%2Fmustafaakin.dev%2Fposts%2F2020-04-26-using-jsonnet-to-generate-dynamic-tekton-pipelines-in-kubernetes%2F%5D%5BUsing%20Jsonnet%20to%20Generate%20Dynamic%20Tekton%20Pipelines%20in%20Kubernetes%20%C2%B7%20Mustafa%20Ak%C4%B1n%5D%5D">
189<p>
190<span class="timestamp-wrapper"><span class="timestamp">[2020-04-28 Tue 00:41]</span></span>
191</p>
192</div>
193</div>
194<div id="outline-container-%5B%5Bhttps%3A%2F%2Fwww.blokje5.dev%2Fposts%2Fcompliance-in-cicd%2F%5D%5BBuilding%20in%20compliance%20in%20your%20CI%2FCD%20pipeline%20with%20conftest%20%C2%B7%20blokje5.dev%5D%5D" class="outline-3">
195<h3 id="%5B%5Bhttps%3A%2F%2Fwww.blokje5.dev%2Fposts%2Fcompliance-in-cicd%2F%5D%5BBuilding%20in%20compliance%20in%20your%20CI%2FCD%20pipeline%20with%20conftest%20%C2%B7%20blokje5.dev%5D%5D"><span class="todo TODO">TODO</span> <a href="https://www.blokje5.dev/posts/compliance-in-cicd/">Building in compliance in your CI/CD pipeline with conftest · blokje5.dev</a></h3>
196<div class="outline-text-3" id="text-%5B%5Bhttps%3A%2F%2Fwww.blokje5.dev%2Fposts%2Fcompliance-in-cicd%2F%5D%5BBuilding%20in%20compliance%20in%20your%20CI%2FCD%20pipeline%20with%20conftest%20%C2%B7%20blokje5.dev%5D%5D">
197<p>
198<span class="timestamp-wrapper"><span class="timestamp">[2020-06-23 Tue 18:07]</span></span>
199</p>
200</div>
201</div>
202<div id="outline-container-%5B%5Bhttps%3A%2F%2Ftechnologists.dev%2Fposts%2Ftekton-jx-pipelines%2F%5D%5BJenkins%20X%20Orchestration%3A%20More%20than%20Tekton%20on%20Steroids%20%3A%3A%20CloudBees%20Technologists%5D%5D" class="outline-3">
203<h3 id="%5B%5Bhttps%3A%2F%2Ftechnologists.dev%2Fposts%2Ftekton-jx-pipelines%2F%5D%5BJenkins%20X%20Orchestration%3A%20More%20than%20Tekton%20on%20Steroids%20%3A%3A%20CloudBees%20Technologists%5D%5D"><span class="todo TODO">TODO</span> <a href="https://technologists.dev/posts/tekton-jx-pipelines/">Jenkins X Orchestration: More than Tekton on Steroids :: CloudBees Technologists</a>&#xa0;&#xa0;&#xa0;<span class="tag"><span class="tekton">tekton</span>&#xa0;<span class="jenkins">jenkins</span>&#xa0;<span class="x">x</span></span></h3>
204<div class="outline-text-3" id="text-%5B%5Bhttps%3A%2F%2Ftechnologists.dev%2Fposts%2Ftekton-jx-pipelines%2F%5D%5BJenkins%20X%20Orchestration%3A%20More%20than%20Tekton%20on%20Steroids%20%3A%3A%20CloudBees%20Technologists%5D%5D">
205<p>
206<span class="timestamp-wrapper"><span class="timestamp">[2020-05-12 Tue 10:36]</span></span>
207</p>
208
209<p>
210Read and gather feedback in issues from there maybe ?
211</p>
212</div>
213</div>
214<div id="outline-container-%5B%5Bhttps%3A%2F%2Fmartinheinz.dev%2Fblog%2F45%5D%5BCloud%20Native%20CI%2FCD%20with%20Tekton%20%E2%80%94%20Laying%20The%20Foundation%5D%5D" class="outline-3">
215<h3 id="%5B%5Bhttps%3A%2F%2Fmartinheinz.dev%2Fblog%2F45%5D%5BCloud%20Native%20CI%2FCD%20with%20Tekton%20%E2%80%94%20Laying%20The%20Foundation%5D%5D"><span class="todo TODO">TODO</span> <a href="https://martinheinz.dev/blog/45">Cloud Native CI/CD with Tekton — Laying The Foundation</a></h3>
216<div class="outline-text-3" id="text-%5B%5Bhttps%3A%2F%2Fmartinheinz.dev%2Fblog%2F45%5D%5BCloud%20Native%20CI%2FCD%20with%20Tekton%20%E2%80%94%20Laying%20The%20Foundation%5D%5D">
217<p>
218<span class="timestamp-wrapper"><span class="timestamp">[2021-03-18 Thu 11:21]</span></span>
219</p>
220</div>
221</div>
222<div id="outline-container-%5B%5Bhttps%3A%2F%2Fmartinheinz.dev%2Fblog%2F47%3Futm_source%3Drss%26utm_medium%3Dreferral%26utm_campaign%3Dblog_post_47%5D%5BMartin%20Heinz%20%7C%20Cloud%20Native%20CI%2FCD%20with%20Tekton%20-%20Building%20Custom%20Tasks%5D%5D" class="outline-3">
223<h3 id="%5B%5Bhttps%3A%2F%2Fmartinheinz.dev%2Fblog%2F47%3Futm_source%3Drss%26utm_medium%3Dreferral%26utm_campaign%3Dblog_post_47%5D%5BMartin%20Heinz%20%7C%20Cloud%20Native%20CI%2FCD%20with%20Tekton%20-%20Building%20Custom%20Tasks%5D%5D"><span class="todo TODO">TODO</span> <a href="https://martinheinz.dev/blog/47?utm_source=rss&amp;utm_medium=referral&amp;utm_campaign=blog_post_47">Martin Heinz | Cloud Native CI/CD with Tekton - Building Custom Tasks</a></h3>
224<div class="outline-text-3" id="text-%5B%5Bhttps%3A%2F%2Fmartinheinz.dev%2Fblog%2F47%3Futm_source%3Drss%26utm_medium%3Dreferral%26utm_campaign%3Dblog_post_47%5D%5BMartin%20Heinz%20%7C%20Cloud%20Native%20CI%2FCD%20with%20Tekton%20-%20Building%20Custom%20Tasks%5D%5D">
225<p>
226<span class="timestamp-wrapper"><span class="timestamp">[2021-04-16 Fri 07:01]</span></span>
227</p>
228</div>
229</div>
230</section>
231</main>
232<footer id="postamble" class="status">
233<footer>
234     <small><a href="/" rel="history">Index</a><a href="/sitemap.html">Sitemap</a><a href="https://dl.sbr.pm/">Files</a></small><br/>
235     <small class='questions'>Questions, comments ? Please use my <a href="https://lists.sr.ht/~vdemeester/public-inbox">public inbox</a> by sending a plain-text email to <a href="mailto:~vdemeester/public-inbox@lists.sr.ht">~vdemeester/public-inbox@lists.sr.ht</a>.</small><br/>
236     <small class='copyright'>
237      Content and design by Vincent Demeester
238      (<a rel='licence' href='http://creativecommons.org/licenses/by-nc-sa/3.0/'>Some rights reserved</a>)
239    </small><br />
240</footer>
241</footer>
242</body>
243</html>