Skip to content

Releases: tektoncd/pipeline

Tekton Pipeline Release v0.4.0 "Aegean Brackenridge"

29 May 18:45
@dlorenc dlorenc
v0.4.0
9c52c69
Compare
Choose a tag to compare
Tekton Pipeline Release v0.4.0 "Aegean Brackenridge" Pre-release
Pre-release

This is the third dogfood released version of Tekton Pipelines, where the images were built, pushed and tagged using a Task!

Changes

Breaking Changes

  • Remove the Trigger field from TaskRun/PipelineRun #857

Features

  • Propagate annotations from Pipeline/Task to PipelineRun/TaskRun #894
  • Generalize messages when TaskRun errs during pod creation #891
  • Allow configuration of PVC size from ConfigMap #866
  • Add support for taskRun to expose digest of built images #721

Fixes

  • Correct setting for kaniko in tasks #883
  • Fix documentation section about installing in custom namespace #881
  • Surface resource constraint problems in TaskRun Status #876
  • Enforce Default TaskRun Timeout #871
  • Update doc to remove taskSpec as an alternative to pipelineRef in a pipelineRun #870

Misc

  • Add Type-Level godocs for API types #921
  • Add godoc for missing Pipeline fields #920
  • Use tektoncd build-base base image for the release #919
  • Cleanup of initializing working dirs #843

Thanks

Thanks to these contributors who contributed to v0.4.0!

Assets 3
Loading

Tekton Pipeline Release v0.3.1 "Chartreux C-3PO" + bug fix

26 Apr 23:01
@bobcatfish bobcatfish
v0.3.1
0dd031e
Compare
Choose a tag to compare
Tekton Pipeline Release v0.3.1 "Chartreux C-3PO" + bug fix Pre-release
Pre-release

🐛 Tekton Pipelines with git ssh bug fixed 🐛

Thanks

Assets 3
Loading

Tekton Pipelines release v0.3.0 "Chartreux C-3PO"

26 Apr 15:14
@vdemeester vdemeester
v0.3.0
e0fed7f
Compare
Choose a tag to compare
Tekton Pipelines release v0.3.0 "Chartreux C-3PO" Pre-release
Pre-release

🎉 Tekton Pipelines with containerTemplate and better resources limit handling 🎉

This is the second dogfood released version of Tekton Pipelines, where the images were built, pushed and tagged using a Task!

Changes

Features

  • Add additionalPrinterColumns to taskrun CRD (#694)
    kubectl get taskruns now gives more information like Type, Status, StartTime,CompletionTime
  • Add additionalPrinterColumns to pipelinerun CRD (#695, #730)
    kubectl get pipelineruns now gives more information like Type, Status, StartTime,CompletionTime
  • Define a minimal PodSecurityPolicy for Tekton components (#703, #718)
  • Make generated pods only request the maximum necessary resources (#723)
    Set CPU, memory, and ephemeral storage resource requests for each
    step in a Task to zero if the step does not have the largest resource
    request out of all steps in the Task. This ensures that the Pod that
    executes the Task will only request the resources necessary to
    execute any single step in the Task, rather than requesting the sum
    of all of the step's resource requests, and is safe because Tekton
    executes steps sequentially rather than all at once.
  • Adds shortname for taskrun and pipelinerun (#743)
    Add short names to taskrun and pipelinerun resources.
    User can use kubectl <action> tr ... to deal with taskruns
    and kubectl <action> pr ... to deal with pipelineruns.
  • Support Pod tolerations in PipelineRun and TaskRun (#707)
  • Adds containerTemplate to TaskSpec, allowing for configuration of a Container to be used as the basis for all steps within the Task. (#767)
  • Add a command line option to the controller for specifying a single namespace to watch, rather than watching all namespaces. (#784)

Fixes

  • Bind webhook controller to a non priviliged port (#720)
  • Fixes bug where sometimes TaskRun timeouts are dropped and the TaskRun may continue executing indefinitely (#780)
  • TaskRun startTime is now determined by the start of reconciliation and is not tied to the creation time of the underlying Pod(s) (#780)
  • Use gsutil rsync instead of cp for updating storage resource, handling the case where the bucket is empy and dir type is used. (#737)
  • Fix CompletionTime missing in TaskRun status (#740)
  • Wrap nop final step with entrypoint, Build success only happens if the task really succeeded (#748)
  • git-init don't assume the image is running as root (#747)
  • Fix propagation of concurrent TaskRun status to failed PipelineRuns (#757)
  • Recreate TaskRun pods on deletion. (#758)

Misc

  • Add a section for installing Tekton Pipelines on OpenShift (#699)
  • Remove some mentions of "knative" and "build-pipeline" (#722)
  • Skip some tests if KO_DOCKER_REPO is missing… (#710)
  • Updating some tests to not require the docker socket (#716)
  • Update some dependencies (#739)
  • Move to the v1beta1 Conditions implementation. (#744)
  • Add the step name in taskrun status (#657)

Thanks

Thanks to these contributors who contributed to v0.3.0!

Extra shout-out for awesome release notes:

Assets 3
Loading

Tekton Pipelines release v0.2.0

28 Mar 01:45
@bobcatfish bobcatfish
v0.2.0
7c43fba
Compare
Choose a tag to compare
Tekton Pipelines release v0.2.0 Pre-release
Pre-release

🎉 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 to deployments/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 from TaskRun 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!

Extra shout-out for awesome release notes:

Assets 3
Loading

Tekton Pipelines release v0.1.0

20 Feb 19:36
@imjasonh imjasonh
v0.1.0
c1500fa
Compare
Choose a tag to compare
Tekton Pipelines release v0.1.0 Pre-release
Pre-release

🎉 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 define steps (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 templating steps
  • Pipelines combine Tasks 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 templating Task 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 and Pipelines can be used repeatedly by instantiating PipelineRuns and TaskRuns, which will cause these to execute.
    • Runs can be executed with user specified ServiceAccounts
    • Runs can be cancelled

Fixes

n/a

Misc

n/a

Assets 3
Loading