Releases: tektoncd/pipeline
Releases · tektoncd/pipeline
Tekton Pipelines release v0.2.0
🎉 Tekton Pipelines with Graphs; without init containers! 🎉
This is the first dogfood released version of Tekton Pipelines, where the images were built, pushed and tagged using a Task!
Changes
Features
- ✨ Allow default system namespace to be overridden using an env var (#427)
- ✨ Use DAG (graph) based execution for Pipelines instead of linear one (#473, #578 )
- ✨ Use truncated base TaskRun name for lookup (#565)
- ✨ The containers executing the Task steps are changed from using InitContainers to Containers in the TaskRun pod. This is achieved by wrapping each container by a custom binary entrypoint to manage the order of the steps. As such, it is always recommended to explicitly specify a command for a Task step. If a step's image is in a private registry, a ServiceAccount with ImagePullSecrets should be provided in the Task (#564, #620, #634, #647, #686, #687)
- ✨ Pipeline doesn't depend on knative/build anymore 💃 (#636, #648)
- ✨ Update taskrun/pipelinerun timeout logic to not rely on resync behavior (#621, #674, #681)
- ✨ cmd/git-init: check for errors or at least log them (#677)
Fixes
- 🐛 Make sure TaskSpec step container names aren't too long (#550)
- 🐛 Arbitrary git commits can now be specified in Git PipelineResources (previously it only supported commits which can be
git fetch
-ed) (#555) - 🐛 PipelineResources storage GCS for directories now preserves directory structures during copies. (#566)
- 🐛 Updates
tekton-pipelines-admin
clusterrole to have full access todeployments/finalizers
(#572) - 🐛 Container names must end with an alphanumeric character (#580)
- 🐛 ServiceAccount without ImagePullSecrets should not fail to fetch (#585)
- 🐛 Fixes RBAC permissions for task and pipeline runs for openshift (#583)
- 🐛 Port duplicate pod test from knative/build 🏗 (#603)
- 🐛 Use full command field for internal containers (#605)
Misc
- 🔨 Remove the
logsURL
field fromTaskRun
status. This field was never populated and was leftover from the original POC version of the API. #107 may add something like this in the future but that design remains TBD (#563) - ⏫ Bump kubernetes dependecies to 1.12.6 (#662)
Thanks
Thanks to these contributors who contributed to v0.2.0!
- ❤️ @abayer
- ❤️ @cagiti
- ❤️ @chmouel
- ❤️ @Conky5
- ❤️ @bobcatfish
- ❤️ @dlorenc
- ❤️ @dibbles
- ❤️ @hrishin
- ❤️ @imjasonh
- ❤️ @khrm
- ❤️ @skeeey
- ❤️ @mattmoor-sockpuppet
- ❤️ @mikeykhalil
- ❤️ @pivotal-nader-ziada
- ❤️ @nbarthwal
- ❤️ @rawlingsj
- ❤️ @rhuss
- ❤️ @shashwathi
- ❤️ @sthaha
- ❤️ @vbatts
- ❤️ @vdemeester
- ❤️ @assertion
Extra shout-out for awesome release notes:
Tekton Pipelines release v0.1.0
🎉 First Tekton Pipelines Release! 🎉
This is the very first release of Tekton Pipelines, which has built on the concept of the Build CRD, allowing users to declare typed inputs and outputs, and to combine multiple Builds (now called Tasks
) into a Pipeline
.
Features
Tasks
allow users to definesteps
(i.e. container images)- Steps which can be executed against typed Inputs and parameters to produce Outputs
- Cluster wide
ClusterTasks
are supported - They can declare
Parameters
which can be used in templatingsteps
Pipelines
combineTasks
together- Optionally they linking inputs and outputs between Tasks
- Tasks are executed sequentially in the order they are declared in the Pipeline.
- They can declare
Parameters
which can be used in templatingTask
usage
PipelineResources
are used as inputs and outputs. The following types are supported:- Git
- Image (templating of attributes only)
- Kubernetes Cluster
- Storage (currently only GCS)
Tasks
andPipelines
can be used repeatedly by instantiatingPipelineRuns
andTaskRuns
, which will cause these to execute.- Runs can be executed with user specified
ServiceAccounts
- Runs can be cancelled
- Runs can be executed with user specified
Fixes
n/a
Misc
n/a