A cloud-native Pipeline resource.
APACHE-2.0 License
Bot releases are visible (Hide)
Published by tekton-robot about 4 years ago
-Docs @ v0.15.1
-Examples @ v0.15.1
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.15.1/release.yaml
Thanks to these contributors who contributed to v0.15.1!
Published by tekton-robot about 4 years ago
Run
CRD, more variables and better docs ๐-Docs @ v0.15.0
-Examples @ v0.15.0
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.15.0/release.yaml
๐ฃ The minimum Kubernetes version is now 1.16. ๐ฃ
There is a known issue with PullRequest Resources in 0.15.0: Tasks that write a pr.json
file to be used by an output PullRequest PipelineResource will see permission errors when run: The output PullRequest Resource will attempt to read the pr.json
file but will not be able to because the injected PullRequest Step is not running as root
. To workaround this issue in the short term you can modify permissions on the pr.json
file to be world-readable (e.g. run chmod 777
on the pr.json
file in your Step). A 0.15 point release is planned to address this issue.
โจ Use cloud event native retries for cloud event pipeline resource (#3003)
Cloud events sent via CloudEventPipelineResource
now use retries with backoff.
โจ Add pipeline run support for cloud events (#2938)
Add cloud events for pipeline runs via the configuration option default-cloud-events-sink
.
When the default sink is setup, cloud events are sent, else they're disabled.
Send cloud events (when enabled) from the pipeline run and controller, for all non-error
events that are already notified via k8s events.
โจ Add Default TaskRun Workspace Bindings to config-default (#2930)
Users can now set a default Workspace
configuration for any Workspaces
that a Task declares but that a TaskRun does not explicitly provide. It can be set in the config-defaults
ConfigMap in default-task-run-workspace-binding
.
โจ Add namespace variable interpolation for pipelinerun namespace and (#2926)
Add namespace variable interpolation in context.
for pipelinerun namespace and taskrun namespace.
โจ Wire up webhook validation for Run objects (#2916)
โจ Define a helper method pkg/controller.FilterRunRef (#2915)
โจ Define v1alpha1 Run type and generated scaffolding (#2871)
Introduce the Run
CRD. The new CRD will support the definition of new
kind of Tasks to be integrated in the pipelines.
Run
s are an experimental alpha feature and should be expected to change
in breaking ways or even be removed.
Run
s are not currently integrated with Pipelines, and require a running
third-party controller to actually perform any work. Without a third-party
controller, Run
s will just exist without a status indefinitely.
โจ Validate TaskRun compatibility with the Affinity Assistant (#2885)
A TaskRun that mount more than one PVC-backed workspace is incompatible
with the Affinity Assistant. Validation has been added to handle this case.
โจ Allow variable substitution inside csi volumes parameters (#2643)
This PR allow to use parameters in CSI volume parameters.
โจ PR upload validates comment file extension (#2462)
Comment files under a PullRequest need to have either:
None this time.
None this time.
[Fill list here]
Condition
documentation for clarity and flow. (#2867)Thanks to these contributors who contributed to v0.15.0!
Extra shout-out for awesome release notes:
Published by tekton-robot about 4 years ago
-Docs @ v0.14.3
-Examples @ v0.14.3
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.14.3/release.yaml
Users need to pass in default parameter values or provide the required parameters in Pipeline
spec as they now get validated by the controller.
The creds-init
step is gone and its behavior is now handle by the entrypoint. This shouldn't have any impact except running as the same user as the step.
Thanks to these contributors who cFix a panic in the pipeline controller that may happen when a pipeline hangs in starting state, because of a malformed condition name.ontributed to v0.14.3!
Published by tekton-robot over 4 years ago
-Docs @ v0.14.2
-Examples @ v0.14.2
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.14.2/release.yaml
Users need to pass in default parameter values or provide the required parameters in Pipeline
spec as they now get validated by the controller.
The creds-init
step is gone and its behavior is now handle by the entrypoint. This shouldn't have any impact except running as the same user as the step.
Thanks to these contributors who contributed to v0.14.2!
Published by tekton-robot over 4 years ago
-Docs @ v0.14.1
-Examples @ v0.14.1
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.14.1/release.yaml
Users need to pass in default parameter values or provide the required parameters in Pipeline
spec as they now get validated by the controller.
The creds-init
step is gone and its behavior is now handle by the entrypoint. This shouldn't have any impact except running as the same user as the step.
Thanks to these contributors who contributed to v0.14.1!
Published by tekton-robot over 4 years ago
-Docs @ v0.14.0
-Examples @ v0.14.0
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.14.0/release.yaml
Users need to pass in default parameter values or provide the required parameters in Pipeline
ย spec as they now get validated by the controller.
The creds-init
step is gone and its behavior is now handle by the entrypoint. This shouldn't have any impact except running as the same user as the step.
โจ Add expansion of context.(pipeline|pipelinerun|task|taskRun).name and add tests (#2880)
$context.(task|taskRun|pipeline|pipelineRun).name
can be used to reference the appropriate name when in pipelineRuns and taskRuns
โจ Finish setting up events for pipeline runs (#2874)
The pipeline run controller now emits a k8s event every time that a pipeline is started.
โจ Start emitting CloudEvents for TaskRuns (#2837)
Add a new configuration option default-cloud-events-sink
in the defaults config map. This options allows setting a default sink for cloud events. If the default sink is setup, cloud events are sent, else they're disabled.
Send cloud events (when enabled) from the task run and controller, for all non-error events that are already notified via k8s events.
โจ Set pipeline status when all tasks complete (#2774)
In case of task run failure or cancellation, the pipeline run stops scheduling new tasks like before. The status is marked as failed however only once all the task runs already scheduled are complete.
A new reason "PipelineRunStopping" indicate that the pipeline run has found a failure and is waiting for task runs to complete.
โจ Migrate the PipelineRun controller to genreconciler. (#2760)
โจ Validate PipelineRun Parameters (#2719)
โจ Add support for more cloud events (#2677)
The cloudevent message type strings change from "dev.tekton.event.task." to "dev.tekton.event.taskrun." for events produced by the CloudEventPipelineResource
.
โจ implementing pipeline level finally (#2661)
Users can now specify Tasks within a Pipeline that will always execute, even if Tasks fail, via the new finally
clause
โจ adding finally type (without implementation) at the pipeline level (#2650)
Introducing a new clause under pipeline
named finally
where users can specify a list of tasks that will always execute, even if pipeline tasks fail. Adding a new type and its validation here, stay tuned for this functionality. Without implementing the functionality, a list of tasks under finally
are validated but not executed at all.
โจ Introduce config map watcher for feature flags (#2637)
๐จ The TaskRun.Status.ResourceResults.ResourceRef
field is deprecated and will be removed.
From Fix PipelineResource name handling. (#2697)
The TaskRun.Status.ResourceResults field now contains a new field called "ResourceName" that points to the name of the PipelineResourceBinding.
The TaskRun.Status.ResourcesResults.ResourceRef.Name field points to this same object. This field is now redundant and will be removed in a future release.
The ClusterResource has been updated to write it's kubeconfig to the correct location on disk. Previously it was written to a location under /workspace/input/, instead of the correct /workspace/input/. If you hardcode resource paths in your tasks, you will need to update these. If you refer to paths by interpolation ( $(resources.inputs.) ), you do not need to make any changes.
In current release:
๐จ Validate PipelineRun Parameters (#2719)
Warning: backwards incompatible change that will force users to pass in default parameter values or provide the required parameters.
๐ cloudevent: make sure we enter the channel beforeโฆ (#2895)
๐ Emit event only once (#2860)
๐ Fix pipelinerun_taskrun_duration_seconds metric (#2849)
๐ Activate SA creds before running ko (#2847)
๐ Add the missing RBAC for leaderelection (#2841)
๐ Fix git-init in case master
is not the default branch (#2835)
The Git PipelineResource now inspects remote repository to determine the correct default branch to use when no revision has been specified.
๐ Don't require pointer to binding (#2834)
๐ Return error if there are multiple same name params (#2817)
After this change it is not allowed to have multiple parameters with the same name within pipeline spec.
๐ Pass port to ssh-keyscan when known_hosts not provided (#2803)
Specifying a git ssh server url with custom port previously failed during credentials initialization if a known_hosts field was not specified in the Secret. This has been fixed.
๐ Remove tag+digest on shell-image ๐ถ (#2781)
Fix shell-image reference to not include the tag in addition to the digest in order to fix the *.notags.yaml
release files
๐ StatefulSet is sensitive to long names - use a hashed name (#2768)
There was a problem with long names for WorkspaceName+PipelineRunName, it could only be up to 33 chars. This commit uses a hashed name for the Affinity Assistant with a consistent length.
๐ Disentangle metric reporting from the actual reconciler. (#2762)
๐ Fix PipelineResource name handling. (#2697)
The TaskRun.Status.ResourceResults field now contains a new field called "ResourceName" that points to the name of the PipelineResourceBinding.
The TaskRun.Status.ResourcesResults.ResourceRef.Name field points to this same object. This field is now redundant and will be removed in a future release.
The ClusterResource has been updated to write it's kubeconfig to the correct location on disk. Previously it was written to a location under /workspace/input/, instead of the correct /workspace/input/. If you hardcode resource paths in your tasks, you will need to update these. If you refer to paths by interpolation ( $(resources.inputs.) ), you do not need to make any changes.
Both paths will work for this release, but you will need to update your Task definitions by a future release.
๐ Remove creds-init initContainer (#2671)
Tekton's creds-init initContainer has been removed and will no longer show up in TaskRun Pods. Credentials from annotated Secrets will continue to be mounted and placed in Step containers' home directory.
๐ Refactoring in sidecar test (#2733)
go test
(#2685)Thanks to these contributors who contributed to v0.14.0!
Extra shout-out for awesome release notes:
finally
feature ๐คPublished by tekton-robot over 4 years ago
-Docs @ v0.13.2
-Examples @ v0.13.2
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.13.2/release.yaml
none
Thanks to these contributors who contributed to v0.13.2!
Published by tekton-robot over 4 years ago
-Docs @ v0.13.1
-Examples @ v0.13.1
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.13.1/release.yaml
n/a
Thanks for the quick bug reports ๐ป :
Thanks to these contributors who contributed to v0.13.1!
Published by tekton-robot over 4 years ago
-Docs @ v0.13.0
-Examples @ v0.13.0
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.13.0/release.yaml
None this time!
None this time!
Track ongoing deprecation notices.
None this time!
tekton.dev/conditionName
label on TaskRun
that back Conditions
that contains the name of the Condition
. (#2579)Thanks to these contributors who contributed to v0.13.0!
Published by tekton-robot over 4 years ago
-Docs @ v0.12.1
-Examples @ v0.12.1
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.12.1/release.yaml
N/A
[Fill list here]
Thanks to these contributors who contributed to v0.12.1!
Extra shout-out for awesome release notes:
Published by tekton-robot over 4 years ago
-Docs @ v0.12.0
-Examples @ v0.12.0
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.12.0/release.yaml
The controller RBAC was split into cluster-wide and tenant roles.
This should not have an impact on upgrade unless roles where previously customized.
tekton.dev/task
label is deprecated on ClusterTasks
--upgrade
to ./hack/update-deps.sh
(#2133)results
sections. (#2459)Thanks to these contributors who contributed to v0.12.0!
Extra shout-out for awesome release notes:
Published by afrittoli over 4 years ago
-Docs @ v0.11.3
-Examples @ v0.11.3
0.11.3 is likely to be the final patch release before 0.12. Included here is a fix for Timeouts in PipelineTasks and several fixes for Task Results. This release also adds support for using Task Results in the parameters of Conditions.
๐จ If you are upgrading from a version of Tekton Pipelines older than v0.11.0 then you may need to delete your existing tekton-pipeline deployments before applying v0.11.3.
Thanks to these contributors who contributed to v0.11.3!
Published by afrittoli over 4 years ago
-Docs @ v0.11.2
-Examples @ v0.11.2
๐จ If you are upgrading from a version of Tekton Pipelines older than v0.11.0 then you may need to delete your existing tekton-pipeline deployments before applying v0.11.2.
Tasks
documentation for clarity and flow. #2317Thanks to these contributors who contributed to v0.11.2!
Published by afrittoli over 4 years ago
This release fixes a bug with default timeouts. The default-timeout-minutes
field in the config-defaults
ConfigMap was being ignored. Upgrade to this release to have the default timeout respected in TaskRuns and PipelineRuns again.
-Docs @ v0.11.1
-Examples @ v0.11.1
๐จ If you are upgrading from a version of Tekton Pipelines older than v0.11.0 then you may need to delete your existing tekton-pipeline deployments before applying v0.11.1.
PipelineRuns
does not work properly in this release. A cancelled PipelineRun
should cancel any of its executing TaskRuns
. However, currently, any TaskRuns
that are executing when a PipelineRun
is cancelled will continue until they exit on their own. Follow Issue 2337 for updates.Thanks to these contributors who contributed to v0.11.1!
Published by afrittoli over 4 years ago
This release is the first official Tekton Pipelines Beta.
If you've been following along with prior release candidates there have been no code changes since yesterday's release of RC4. The only noticeable change is that applying the latest version of Tekton to your clusters will now yield a controller with version label of "v0.11.0" instead of "v0.11.0-rc4".
Installation one-liner:
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.11.0/release.yaml
๐จ The minimum version of Kubernetes required to run Tekton Pipelines is now 1.15.
๐จ If you are upgrading from an older version of Tekton Pipelines you may need to delete your existing tekton-pipeline
deployments before apply
ing v0.11.0
.
๐จ Submitting the same v1alpha1 Tasks more than once results in errors. Use kubectl replace
instead of kubectl apply
.
๐จ PipelineResources
are not moving to Beta with Tekton's other types
We do not plan to promote PipelineResources
into Beta. They will continue to work as part of Beta but their use is discouraged when possible. We are progressively adding documentation and Catalog Tasks to help users migrate away from them:
PipelineResource
.PipelineResource
.๐จ The $HOME
env var and workingDir
of Steps will change in the next release (#2044)
Tekton currently overwrites the HOME
environment variable in a Step's container to always be /tekton/home
and the workingDir
field of the Step's image to always be /workspace
. This behaviour will change in the next release: those two fields will be left untouched by Tekton, using whatever settings are defined in the container image and Task's YAML. We have introduced a new ConfigMap, named feature-flags
, that allows you to use this new behaviour now:
disable-home-env-overwrite
: When this flag is set to "true"
Tekton will allow a Step's image to dictate its own $HOME
directory.disable-working-directory-overwrite
: When this flag is set to "true"
Tekton will allow a Step's image to dictate its own workingDir
.In the next release we plan to flip these flags so that they are opt-out rather than opt-in. At some point in the future we plan to remove support for this overwriting behaviour entirely.
Below is the complete list of changes that have been added to Tekton Pipelines across all of the Beta Release Candidates.
v1beta1
API Version (#2035)Workspaces
documentation. (#2256)Thanks to all those who have contributed to the Beta!
Published by afrittoli over 4 years ago
This is the fourth release towards Beta and includes a few final bug fixes for issues discovered after RC3 went out. This will be the final release before we formally declare Beta ready.
๐จ If you are upgrading from an older version of Tekton you may need to delete your existing tekton-pipeline
deployments before apply
ing the 0.11 release candidates.
๐จ Submitting v1alpha1 Tasks more than once can now result in errors. Submitting a v1alpha1 Task once will work but submitting the same Task again will fail. To work around this problem use kubectl replace
instead of apply
or first delete the Task and then re-apply
it.
This is a side-effect of the way Tekton internally upgrades Tasks from v1alpha1 to v1beta1. This issue will affect any Task that includes inputs.params or inputs.resources. On submission Kubernetes will return an error such as error when applying patch [...] validation failed: expected exactly one, got both: inputs.params, params.
๐จ Please also note that the minimum version of Kubernetes required to run Tekton is now 1.15.
๐จ PipelineResources are not moving to Beta with Tekton's other types
PipelineResources have been a source of some contention within the Tekton community over the past several months. While the abstraction they expose does provide some value they can often be difficult to understand, hard to debug when they go wrong, and are far too limited in number and scope. For these reasons and more we do not plan to promote PipelineResources into Beta and will instead provide a documented migration path for users that does not use the type at all. Towards this goal we have already introduced a git-clone
Task to the Tekton Catalog that provides exactly the same behaviour as the Git PipelineResource and we plan to introduce similar Tasks for all of the other existing PipelineResource types as well.
See the git-clone Task in the catalog.
๐จ The $HOME
env var and workingDir
of Steps will change in the next release
Tekton currently overwrites the HOME
environment variable in a Step's container to always be /tekton/home
and the workingDir
field of the Step's image to always be /workspace
. This behaviour is problematic when a container depends on those values to be something specific for it to run correctly.
In this release we are leaving Tekton's default behaviour alone but have introduced a new ConfigMap, named feature-flags
, that allows you to disable it. In the next release we plan to flip this behaviour so that it is opt-in rather than opt-out. At some point in the future we plan to remove support for this overwriting behaviour entirely. (#2044).
In current release:
๐จ The minimum required version of Kubernetes is now 1.15
Bump kubernetes to 1.16.5 and knative/pkg to release-0.12 (#1894)
๐จ Submitting v1alpha1 Tasks more than once can now result in errors. Submitting a v1alpha1
Task once will work but submitting the same Task again will fail.
Thanks to these contributors who contributed to v0.11.0-rc4!
Published by afrittoli over 4 years ago
This is the third release towards Beta and includes bug fixes for issues discovered after RC2 went out. This is planned to be the final release before we formally declare Beta ready.
๐จ If you are upgrading from an older version of Tekton you may need to delete your existing tekton-pipeline
deployments before apply
ing the 0.11 release candidates.
๐จ Submitting v1alpha1 Tasks more than once can now result in errors. Submitting a v1alpha1 Task once will work but submitting the same Task again will fail. To work around this problem use kubectl replace
instead of apply
or first delete the Task and then re-apply
it.
This is a side-effect of the way Tekton internally upgrades Tasks from v1alpha1 to v1beta1. This issue will affect any Task that includes inputs.params or inputs.resources. On submission Kubernetes will return an error such as error when applying patch [...] validation failed: expected exactly one, got both: inputs.params, params.
๐จ Please also note that the minimum version of Kubernetes required to run Tekton is now 1.15.
-Docs @ v0.11.0-rc3
-Examples @ v0.11.0-rc3
๐จ PipelineResources are not moving to Beta with Tekton's other types
PipelineResources have been a source of some contention within the Tekton community over the past several months. While the abstraction they expose does provide some value they can often be difficult to understand, hard to debug when they go wrong, and are far too limited in number and scope. For these reasons and more we do not plan to promote PipelineResources into Beta and will instead provide a documented migration path for users that does not use the type at all. Towards this goal we have already introduced a git-clone
Task to the Tekton Catalog that provides exactly the same behaviour as the Git PipelineResource and we plan to introduce similar Tasks for all of the other existing PipelineResource types as well.
See the git-clone Task in the catalog.
๐จ The $HOME
env var and workingDir
of Steps will change in the next release
Tekton currently overwrites the HOME
environment variable in a Step's container to always be /tekton/home
and the workingDir
field of the Step's image to always be /workspace
. This behaviour is problematic when a container depends on those values to be something specific for it to run correctly.
In this release we are leaving Tekton's default behaviour alone but have introduced a new ConfigMap, named feature-flags
, that allows you to disable it. In the next release we plan to flip this behaviour so that it is opt-in rather than opt-out. At some point in the future we plan to remove support for this overwriting behaviour entirely. (#2044).
In current release:
๐จ The minimum required version of Kubernetes is now 1.15
Bump kubernetes to 1.16.5 and knative/pkg to release-0.12 (#1894)
๐จ Submitting v1alpha1 Tasks more than once can now result in errors. Submitting a v1alpha1
Task once will work but submitting the same Task again will fail.
Workspaces
documentation. (#2256)Thanks to these contributors who contributed to v0.11.0-rc3!
Published by afrittoli over 4 years ago
-Docs @ v0.10.2
-Examples @ v0.10.2
Published by afrittoli over 4 years ago
This is the second release towards Beta and includes bug fixes for issues discovered after RC1 went out. There will be at least one more release candidate before the actual Beta.
๐จ If you are upgrading from an older version of Tekton you may need to delete your existing tekton-pipeline
deployments before apply
ing the 0.11 release candidates.
๐จ Submitting v1alpha1 Tasks more than once can now result in errors. Submitting a v1alpha1 Task once will work but submitting the same Task again will fail. To work around this problem use kubectl replace
instead of apply
or first delete the Task and then re-apply
it.
This is a side-effect of the way Tekton internally upgrades Tasks from v1alpha1 to v1beta1. This issue will affect any Task that includes inputs.params or inputs.resources. On submission Kubernetes will return an error such as error when applying patch [...] validation failed: expected exactly one, got both: inputs.params, params.
๐จ Please also note that the minimum version of Kubernetes required to run Tekton is now 1.15.
-Docs @ v0.11.0-rc2
-Examples @ v0.11.0-rc2
๐จ PipelineResources are not moving to Beta with Tekton's other types
PipelineResources have been a source of some contention within the Tekton community over the past several months. While the abstraction they expose does provide some value they can often be difficult to understand, hard to debug when they go wrong, and are far too limited in number and scope. For these reasons and more we do not plan to promote PipelineResources into Beta and will instead provide a documented migration path for users that does not use the type at all. Towards this goal we have already introduced a git-clone
Task to the Tekton Catalog that provides exactly the same behaviour as the Git PipelineResource and we plan to introduce similar Tasks for all of the other existing PipelineResource types as well.
See the git-clone Task in the catalog.
๐จ The $HOME
env var and workingDir
of Steps will change in the next release
Tekton currently overwrites the HOME
environment variable in a Step's container to always be /tekton/home
and the workingDir
field of the Step's image to always be /workspace
. This behaviour is problematic when a container depends on those values to be something specific for it to run correctly.
In this release we are leaving Tekton's default behaviour alone but have introduced a new ConfigMap, named feature-flags
, that allows you to disable it. In the next release we plan to flip this behaviour so that it is opt-in rather than opt-out. At some point in the future we plan to remove support for this overwriting behaviour entirely. (#2044).
In current release:
๐จ The minimum required version of Kubernetes is now 1.15
Bump kubernetes to 1.16.5 and knative/pkg to release-0.12 (#1894)
๐จ Submitting v1alpha1 Tasks more than once can now result in errors. Submitting a v1alpha1
Task once will work but submitting the same Task again will fail.
Thanks to these contributors who contributed to v0.11.0-rc2!
Published by afrittoli over 4 years ago
With this release Tekton Pipelines introduces a new apiVersion, v1beta1
. While the v1alpha1
version is continuing to be supported at this time we'd like to encourage anyone integrating with Pipelines to be aware of the upcoming API change and begin thinking about migrating over to the beta API. Documentation on migrating will be forthcoming, this release simply introduces the new version and allows us to publicise it.
Over the coming weeks we'll be working with the other Tekton projects to migrate their integrations to v1beta1
and fixing problems as they arise in subsequent Release Candidates.
๐จ If you are upgrading from an older version of Tekton you may need to delete your existing tekton-pipeline
deployments before apply
ing the 0.11 release candidates.
๐จ Submitting v1alpha1 Tasks more than once can now result in errors. Submitting a v1alpha1
Task once will work but submitting the same Task again will fail. To work around this problem first delete the Task and then reapply it.
This is a side-effect of the way Tekton internally upgrades Tasks from
v1alpha1
tov1beta1
. This issue will affect any Task that includesinputs.params
orinputs.resources
. On submission Kubernetes will return an error such aserror when applying patch [...] validation failed: expected exactly one, got both: inputs.params, params
.
๐จ Please also note that the minimum version of Kubernetes required to run Tekton is now 1.15.
โจ Introduce the v1beta1
API Version
Tekton Pipelines has introduced a new API version, v1beta1
, with improvements to some of its APIs and Types.
Add ClusterTask to v1alpha2 (#1946)
Port TaskResults and TaskRunResults to v1alpha2 (#1948)
Port Workspace in pipeline support to v1alpha2 (#1949)
Add PipelineRun types to v1alpha2 (#1955)
Add LimitRangeName to v1alpha2.PipelineRun tulip (#2009)
Task, ClusterTask and Pipeline auto-conversion from v1alpha1 to v1alpha2 (#2002)
TaskRun, and PipelineRun auto-conversion from v1alpha1 to v1alpha2 (#2025)
Expose v1beta1 to the world (#2035)
โจ Improved LimitRange support
Tekton Pipelines now plays more nicely with LimitRanges in a namespace when creating new Pods for TaskRuns.
Leave Max Container Request Values at Original Indices (#1937)
Check for LimitRange Minimum for TaskRun Container Requests (#1991)
Add LimitRange Examples for PipelineRun and TaskRun (#2004)
Pods created by TaskRuns will now respect any LimitRange minimums that exist in the namespace that the Pod runs in (#2020).
โจ Pipeline Resources can now be marked as optional
PipelineResources can now be declared as optional, allowing Tasks to be more flexible in their handling of input resources.
Enabling Pipeline Resources to be marked as Optional (#1910)
โจ Data can now be shared between Tasks using Task Results and Task Params
A Pipeline can now feed Task Results into other Tasks through their Params. It is now much easier to pass small pieces of data through a Pipeline.
Update task run status with results (#1921)
Adding substitution for result path variable (#2018)
Adding pipeline results (#2042)
Make results folder writable (Fix for #2131) (#2143)
โจ Tekton Pipelines can be configured to no longer overwrite the HOME environment variable and workingDir of Steps
In the next release of Tekton this behaviour will become the default!
Allow disabling implicit HOME overwrite (#2044)
Add handling of working directory (#2115)
โจ Sidecars now support Script mode, just like in Task Steps
Add Script Support to Sidecars (#1987)
โจ TaskRuns can now specify a different Scheduler Name in their podTemplate
Add SchedulerName to TaskRunSpec (#1790)
โจ JSONPath-like Star Array Notation can now be used in variable substitutions
Adds Basic Support for Star Array Notation (#2085)
โจ The Tekton Controller can now be configured to monitor an individual namespace
Allow controller to watch a specified namespace (#2144)
๐จ PipelineResources are not moving to Beta with Tekton's other types
PipelineResources have been a source of some contention within the Tekton community over the past several months. While the abstraction they expose does provide some value they can often be difficult to understand, hard to debug when they go wrong, and are far too limited in number and scope. For these reasons and more we do not plan to promote PipelineResources into Beta and will instead provide a documented migration path for users that does not use the type at all. Towards this goal we have already introduced a git-clone
Task to the Tekton Catalog that provides exactly the same behaviour as the Git PipelineResource and we plan to introduce similar Tasks for all of the other existing PipelineResource types as well.
See the git-clone Task in the catalog.
๐จ The $HOME
env var and workingDir
of Steps will change in the next release
Tekton currently overwrites the HOME
environment variable in a Step's container to always be /tekton/home
and the workingDir
field of the Step's image to always be /workspace
. This behaviour is problematic when a container depends on those values to be something specific for it to run correctly.
In this release we are leaving Tekton's default behaviour alone but have introduced a new ConfigMap, named feature-flags
, that allows you to disable it. In the next release we plan to flip this behaviour so that it is opt-in rather than opt-out. At some point in the future we plan to remove support for this overwriting behaviour entirely. (#2044).
In current release:
๐จ The minimum required version of Kubernetes is now 1.15
Bump kubernetes to 1.16.5 and knative/pkg to release-0.12 (#1894)
๐จ Submitting v1alpha1 Tasks more than once can now result in errors. Submitting a v1alpha1
Task once will work but submitting the same Task again will fail. To work around this problem first delete the Task and then reapply it.
Thanks to these contributors who contributed to v0.11.0-rc1!