A cloud-native Pipeline resource.
APACHE-2.0 License
Bot releases are hidden (Show)
Published by bobcatfish over 5 years ago
🐛 Fix git-init failures with git ssh credentials #803
🔨 Style improvements around omitempty
(#798)
omitempty
fixesPublished by vdemeester over 5 years ago
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!
kubectl get taskruns
now gives more information like Type
, Status
, StartTime
,CompletionTime
kubectl get pipelineruns
now gives more information like Type
, Status
, StartTime
,CompletionTime
taskrun
and pipelinerun
resources.kubectl <action> tr ...
to deal with taskruns
kubectl <action> pr ...
to deal with pipelineruns
.PipelineRun
and TaskRun
(#707)containerTemplate
to TaskSpec
, allowing for configuration of a Container
to be used as the basis for all steps within the Task
. (#767)dir
type is used. (#737)Build success
only happens if the task really succeeded (#748)Thanks to these contributors who contributed to v0.3.0!
Extra shout-out for awesome release notes:
Published by bobcatfish over 5 years ago
This is the first dogfood released version of Tekton Pipelines, where the images were built, pushed and tagged using a Task!
git fetch
-ed) (#555)tekton-pipelines-admin
clusterrole to have full access to deployments/finalizers
(#572)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)Thanks to these contributors who contributed to v0.2.0!
Extra shout-out for awesome release notes:
Published by imjasonh over 5 years ago
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
.
Tasks
allow users to define steps
(i.e. container images)
ClusterTasks
are supportedParameters
which can be used in templating steps
Pipelines
combine Tasks
together
Parameters
which can be used in templating Task
usagePipelineResources
are used as inputs and outputs. The following types are supported:
Tasks
and Pipelines
can be used repeatedly by instantiating PipelineRuns
and TaskRuns
, which will cause these to execute.
ServiceAccounts
n/a
n/a