├── CONTRIBUTING.md ├── LICENSE ├── OWNERS ├── README.md ├── alibaba └── readme.md ├── antfinancial └── readme.md ├── cloudbees └── readme.md ├── code-of-conduct.md ├── d2iq └── readme.md ├── elastic └── readme.md ├── google └── readme.md ├── ibm └── readme.md ├── netease └── readme.md ├── ozone └── readme.md ├── puppet └── README.md ├── redhat └── README.md ├── tekton-friends.png ├── triggermesh └── README.md └── yametech └── readme.md /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to the friends repo 2 | 3 | Thank you for your interest in contributing! 4 | 5 | This doc is about how to contribute to this repo specifically. For how to 6 | contribute to tektoncd projects in general, see [the overview in our README](README.md) 7 | and the individual `CONTRIBUTING.md` files in each respective project. 8 | 9 | **All contributors must comply with 10 | [the code of conduct](./code-of-conduct.md).** 11 | 12 | PRs are welcome, and will follow 13 | [the tektoncd pull request process](https://github.com/tektoncd/community/blob/master/process.md#pull-request-process). 14 | 15 | To add a new section for your company: 16 | * create a new sub-directory under the `friends` directory, with an appropriate name. 17 | * include a README.md file inside that with whatever information you're able to share. 18 | 19 | Right now we do not enforce any strict schema or format on these README's, but we may in the future. 20 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /OWNERS: -------------------------------------------------------------------------------- 1 | # The OWNERS file is used by prow to automatically merge approved PRs. 2 | 3 | approvers: 4 | - kimsterv 5 | - dlorenc 6 | - vdemeester 7 | - skaegi 8 | - bobcatfish 9 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 |

2 | Tekton Friends logo (Tekton logo with rabbit and dog 3 |

4 | 5 | # Tekton Friends 6 | 7 | Knowing which individuals and companies are involved in the Tekton project and why would benefit the entire Tekton community. 8 | This repository acts as a place that allows members of the ecosystem (known as "Tekton Friends") to self-report in a way that is beneficial to everyone. 9 | 10 | # Contributing 11 | 12 | If you want to contribute to this repository, please see our [contributing](CONTRIBUTING.md) guidelines. 13 | -------------------------------------------------------------------------------- /alibaba/readme.md: -------------------------------------------------------------------------------- 1 | # Alibaba 2 | 3 | - Alibaba is an active user of the Tekton project. The use case goes beyond CI/CD framework. 4 | - In Alibaba, thousands of "middleware" services are being used to support worldscale e-commerce and cloud business. 5 | - All of these services are stateful apps, which is supposed be "nightmare" to manage, managed effortlessly by Operators + CRD. 6 | - Alibaba now uses Tekton to continuously deliver these services across hybrid clouds. 7 | - We implemented Canary Analysis + Progressive Deployment based on Tekton, deliver with strategy and confidence. 8 | - We are dedicated to encouraging using Tekton across teams in a broader world, including testing and SRE teams. 9 | - Not so surprisingly, our SRE team uses Tekton to deploy kubelet, containerd, etc. to the 10k+ nodes cluster in Alibaba. 10 | -------------------------------------------------------------------------------- /antfinancial/readme.md: -------------------------------------------------------------------------------- 1 | # AntFinancial 2 | 3 | - Ant Financial is an active user of the Tekton project. As of now, we use Tekton to run tens of thousands different pipelineRun every day. 4 | - We are building a cloud native BUILD/CI system based on Tekton. 5 | - We build a grpc service to manage the lifecycle of BUILD/CI objects such as pipelineRun instances, pod logs and etc. 6 | - We build and deploy a group of agents to pull those BUILD/CI objects and submit them to Tekton for execution and record their corresponding status. -------------------------------------------------------------------------------- /cloudbees/readme.md: -------------------------------------------------------------------------------- 1 | # CloudBees 2 | 3 | - CloudBees uses Tekton in its [cloud native DevSecOps platform](https://www.cloudbees.com/products/saas-platform) 4 | - We partnered with Google and a host of other companies to create the [Continuous Delivery Foundation](https://cd.foundation/). 5 | - We're excited to be at the forefront of k8s-native continuous delivery. -------------------------------------------------------------------------------- /code-of-conduct.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, gender identity and expression, level of 9 | experience, education, socio-economic status, nationality, personal appearance, 10 | race, religion, or sexual identity and orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | - Using welcoming and inclusive language 18 | - Being respectful of differing viewpoints and experiences 19 | - Gracefully accepting constructive criticism 20 | - Focusing on what is best for the community 21 | - Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | - The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | - Trolling, insulting/derogatory comments, and personal or political attacks 28 | - Public or private harassment 29 | - Publishing others' private information, such as a physical or electronic 30 | address, without explicit permission 31 | - Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ## Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behavior and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behavior. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or reject 41 | comments, commits, code, wiki edits, issues, and other contributions that are 42 | not aligned to this Code of Conduct, or to ban temporarily or permanently any 43 | contributor for other behaviors that they deem inappropriate, threatening, 44 | offensive, or harmful. 45 | 46 | ## Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account, or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | ## Enforcement 56 | 57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 58 | reported by contacting the project team at 59 | tekton-code-of-conduct@googlegroups.com. All complaints will be reviewed and 60 | investigated and will result in a response that is deemed necessary and 61 | appropriate to the circumstances. The project team is obligated to maintain 62 | confidentiality with regard to the reporter of an incident. Further details of 63 | specific enforcement policies may be posted separately. 64 | 65 | Project maintainers who do not follow or enforce the Code of Conduct in good 66 | faith may face temporary or permanent repercussions as determined by other 67 | members of the project's leadership. 68 | 69 | ## Attribution 70 | 71 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 72 | version 1.4, available at 73 | https://www.contributor-covenant.org/version/1/4/code-of-conduct.html 74 | 75 | [homepage]: https://www.contributor-covenant.org -------------------------------------------------------------------------------- /d2iq/readme.md: -------------------------------------------------------------------------------- 1 | # D2iQ 2 | 3 | - D2iQ is actively contributing to the Tekton project and using it as a foundational CI/CD technology for building our Cloud Native CI/CD platform, [Dispatch CI/CD Product](https://d2iq.com/solutions/ksphere/dispatch) for developers building Cloud Native applications on Kubernetes. 4 | - We have invested development resources to contribute to the Tekton project features we believe are beneficial to all members of the community. 5 | - D2iQ strongly supports the community focused effort to improve the Tekton project through open communication and collaboration. 6 | - We are deeply interested in ensuring the Tekton project continues to quickly evolve to be a cornerstone of Open Source and Cloud Native development. 7 | -------------------------------------------------------------------------------- /elastic/readme.md: -------------------------------------------------------------------------------- 1 | # Elastic 2 | 3 | * Elastic is using Tekton Pipeline and Tekton CLI in build and release processes for the Elastic Stack (Elasticsearch, Kibana, Beats, Logstash, APM) and Elastic Solutions. 4 | We have significantly improved our promotion and publishing process by using these Tekton projects. 5 | 6 | * We utilize the Elastic Stack to observe all the Tekton Pods' metrics and logs. 7 | 8 | * We contribute to Tekton development by opening issues and pull requests. -------------------------------------------------------------------------------- /google/readme.md: -------------------------------------------------------------------------------- 1 | # Google 2 | 3 | - Google started the Tekton project and contributes to it heavily 4 | - Our goal for the project is to serve as a set of building blocks for CI/CD systems on top of Kubernetes 5 | - We are interested in making sure it runs great on GCP, GKE and Anthos 6 | - We are passionate about fostering a vibrant ecosystem for Tekton and having a catalog of maintained Tasks that can be shared and reused 7 | 8 | # Kf 9 | 10 | - [Kf](https://github.com/google/kf) is an open source project started by Google. 11 | - Kf uses Tekton to build containers from source code using Buildpacks and Kaniko. 12 | - We're excited to work with Tekton and build an amazing developer experience! 13 | -------------------------------------------------------------------------------- /ibm/readme.md: -------------------------------------------------------------------------------- 1 | # IBM 2 | 3 | - IBM is actively contributing to the Tekton project and using it as the foundation CI/CD technology for building cloud-native applications on Kubernetes in our public and hybrid clouds 4 | - We have invested UX and development resources to contribute to the Tekton Dashboard to make Tekton easy to use for all developers 5 | - IBM strongly supports efforts to standardize CI/CD building blocks as a goal for the Tekton project as well as building a community to share experience and catalog best practices 6 | - We are deeply interested in ensuring the Tekton project quickly evolves to have stable APIs and appropriate release controls to let it be easily consumable 7 | -------------------------------------------------------------------------------- /netease/readme.md: -------------------------------------------------------------------------------- 1 | # NetEase 2 | 3 | - NetEase is a deep user of the Tekton project and we use it on almost all of our cloud native architectures. 4 | - We use it in a number of scenarios, including continuous delivery, GitOps, and Serverless, that have been implemented and used in our business. 5 | - We use a lot of function of Tekton and also implement some supporting components, such as storage-based resource archiving server. 6 | - We are impressed by Tekton's lightness and ease of use, and we are committed to simplifying the deployment and use of the pipeline by this lightweight product, and make it transparent to the end user. 7 | 8 | -------------------------------------------------------------------------------- /ozone/readme.md: -------------------------------------------------------------------------------- 1 | # Ozone 2 | 3 | - Ozone an early adopter of the Tekton project. Our platform is built on Kubernetes and leverages the Tekton framework to provide cloud native Continuous Delivery as-a-service. CD pipelines is helping developers to deploy cloud-native applications and manage infrastructure quickly and more efficiently. 4 | - We actively participate in Tekton meet-ups and encourage our developers to use Tekton in various development environments. 5 | - Ozone is a member of Continuous Delivery Foundation (CDF) and it is in the best interest of our stakeholders that the Tekton project continues to evolve as the best CI/CD system and ensure safe and reliable environment for Cloud Native software delivery. 6 | - For more information please visit https://ozone.one/ 7 | -------------------------------------------------------------------------------- /puppet/README.md: -------------------------------------------------------------------------------- 1 | # Puppet 2 | 3 | * Puppet is building a product to help teams deploy cloud-native applications and manage their infrastructure with event-driven ops workflows. 4 | * It's called Relay and is available at [https://relay.sh](https://relay.sh) 5 | * Relay uses Tekton under the hood as its execution engine. We found that using Tekton accelerated our development timeline by several months due to its capabilities and active community. 6 | * Puppet is a CDF founding member. Our developers and product managers are working upstream on Tekton to fix bugs, implement features, and help define standards in the sig-interoperability working group. 7 | -------------------------------------------------------------------------------- /redhat/README.md: -------------------------------------------------------------------------------- 1 | # Red Hat 2 | 3 | - Red Hat is a dedicated and active contributor to the Tekton project 4 | - Red Hat's interest is for Tekton to serve as the standard CI/CD framework for Kubernetes 5 | - We have contributed and continue to actively work on the Tekton CLI and Tekton Operator among other areas 6 | - We make sure that Tekton works on OpenShift 7 | - We are committed to provide a user-experience around Tekton under the name OpenShift Pipelines while staying true to Tekton standardization efforts in order to encourage and simplify use of Tekton on OpenShift 8 | -------------------------------------------------------------------------------- /tekton-friends.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/tektoncd/friends/87656eec89039f289566ed2fbb1b9bbe1353eec7/tekton-friends.png -------------------------------------------------------------------------------- /triggermesh/README.md: -------------------------------------------------------------------------------- 1 | # TriggerMesh 2 | 3 | - TriggerMesh is a dedicated contributor to Knative and a user of the Tekton project 4 | - We developed [Aktion](https://github.com/triggermesh/aktion) to translate GitHub Action workflows into Tekton Pipelines 5 | - We integrated [Task management](https://docs.triggermesh.io/guides/actions/) into the TriggerMesh cloud 6 | - Our Knative client [`tm`](https://github.com/triggermesh/tm) also supports CRUD operations for Tasks and TaskRuns 7 | - Finally, our source to URL workflow with `tm` makes [use of Tekton](http://triggermesh.com/2019/07/deploying-functions-to-knative-the-serverless-framework-way/) 8 | -------------------------------------------------------------------------------- /yametech/readme.md: -------------------------------------------------------------------------------- 1 | # Yametech 2 | 3 | - Yametech is actively contributing to the Tekton project and using it as a foundational CI/CD technology for building our Cloud Native CI/CD platform, [Compass](https://github.com/yametech/compass) for developers building Cloud Native applications on Kubernetes. 4 | - We build a service to manage the lifecycle of BUILD/CI objects such as pipelineRun instances, pod logs,tekton-store,webhook and etc. --------------------------------------------------------------------------------