Full Code of bregman-arie/howtheydevops for AI

main 8dbd49a36def cached
4 files
37.0 KB
9.9k tokens
1 requests
Download .txt
Repository: bregman-arie/howtheydevops
Branch: main
Commit: 8dbd49a36def
Files: 4
Total size: 37.0 KB

Directory structure:
gitextract_atgcq_0b/

├── LICENSE
├── README.md
├── code-of-conduct.md
└── contributing.md

================================================
FILE CONTENTS
================================================

================================================
FILE: LICENSE
================================================
Creative Commons Legal Code

CC0 1.0 Universal

    CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
    LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
    ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
    INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
    REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
    PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
    THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
    HEREUNDER.

Statement of Purpose

The laws of most jurisdictions throughout the world automatically confer
exclusive Copyright and Related Rights (defined below) upon the creator
and subsequent owner(s) (each and all, an "owner") of an original work of
authorship and/or a database (each, a "Work").

Certain owners wish to permanently relinquish those rights to a Work for
the purpose of contributing to a commons of creative, cultural and
scientific works ("Commons") that the public can reliably and without fear
of later claims of infringement build upon, modify, incorporate in other
works, reuse and redistribute as freely as possible in any form whatsoever
and for any purposes, including without limitation commercial purposes.
These owners may contribute to the Commons to promote the ideal of a free
culture and the further production of creative, cultural and scientific
works, or to gain reputation or greater distribution for their Work in
part through the use and efforts of others.

For these and/or other purposes and motivations, and without any
expectation of additional consideration or compensation, the person
associating CC0 with a Work (the "Affirmer"), to the extent that he or she
is an owner of Copyright and Related Rights in the Work, voluntarily
elects to apply CC0 to the Work and publicly distribute the Work under its
terms, with knowledge of his or her Copyright and Related Rights in the
Work and the meaning and intended legal effect of CC0 on those rights.

1. Copyright and Related Rights. A Work made available under CC0 may be
protected by copyright and related or neighboring rights ("Copyright and
Related Rights"). Copyright and Related Rights include, but are not
limited to, the following:

  i. the right to reproduce, adapt, distribute, perform, display,
     communicate, and translate a Work;
 ii. moral rights retained by the original author(s) and/or performer(s);
iii. publicity and privacy rights pertaining to a person's image or
     likeness depicted in a Work;
 iv. rights protecting against unfair competition in regards to a Work,
     subject to the limitations in paragraph 4(a), below;
  v. rights protecting the extraction, dissemination, use and reuse of data
     in a Work;
 vi. database rights (such as those arising under Directive 96/9/EC of the
     European Parliament and of the Council of 11 March 1996 on the legal
     protection of databases, and under any national implementation
     thereof, including any amended or successor version of such
     directive); and
vii. other similar, equivalent or corresponding rights throughout the
     world based on applicable law or treaty, and any national
     implementations thereof.

2. Waiver. To the greatest extent permitted by, but not in contravention
of, applicable law, Affirmer hereby overtly, fully, permanently,
irrevocably and unconditionally waives, abandons, and surrenders all of
Affirmer's Copyright and Related Rights and associated claims and causes
of action, whether now known or unknown (including existing as well as
future claims and causes of action), in the Work (i) in all territories
worldwide, (ii) for the maximum duration provided by applicable law or
treaty (including future time extensions), (iii) in any current or future
medium and for any number of copies, and (iv) for any purpose whatsoever,
including without limitation commercial, advertising or promotional
purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
member of the public at large and to the detriment of Affirmer's heirs and
successors, fully intending that such Waiver shall not be subject to
revocation, rescission, cancellation, termination, or any other legal or
equitable action to disrupt the quiet enjoyment of the Work by the public
as contemplated by Affirmer's express Statement of Purpose.

3. Public License Fallback. Should any part of the Waiver for any reason
be judged legally invalid or ineffective under applicable law, then the
Waiver shall be preserved to the maximum extent permitted taking into
account Affirmer's express Statement of Purpose. In addition, to the
extent the Waiver is so judged Affirmer hereby grants to each affected
person a royalty-free, non transferable, non sublicensable, non exclusive,
irrevocable and unconditional license to exercise Affirmer's Copyright and
Related Rights in the Work (i) in all territories worldwide, (ii) for the
maximum duration provided by applicable law or treaty (including future
time extensions), (iii) in any current or future medium and for any number
of copies, and (iv) for any purpose whatsoever, including without
limitation commercial, advertising or promotional purposes (the
"License"). The License shall be deemed effective as of the date CC0 was
applied by Affirmer to the Work. Should any part of the License for any
reason be judged legally invalid or ineffective under applicable law, such
partial invalidity or ineffectiveness shall not invalidate the remainder
of the License, and in such case Affirmer hereby affirms that he or she
will not (i) exercise any of his or her remaining Copyright and Related
Rights in the Work or (ii) assert any associated claims and causes of
action with respect to the Work, in either case contrary to Affirmer's
express Statement of Purpose.

4. Limitations and Disclaimers.

 a. No trademark or patent rights held by Affirmer are waived, abandoned,
    surrendered, licensed or otherwise affected by this document.
 b. Affirmer offers the Work as-is and makes no representations or
    warranties of any kind concerning the Work, express, implied,
    statutory or otherwise, including without limitation warranties of
    title, merchantability, fitness for a particular purpose, non
    infringement, or the absence of latent or other defects, accuracy, or
    the present or absence of errors, whether or not discoverable, all to
    the greatest extent permissible under applicable law.
 c. Affirmer disclaims responsibility for clearing rights of other persons
    that may apply to the Work or any use thereof, including without
    limitation any person's Copyright and Related Rights in the Work.
    Further, Affirmer disclaims responsibility for obtaining any necessary
    consents, permissions or other rights required for any use of the
    Work.
 d. Affirmer understands and acknowledges that Creative Commons is not a
    party to this document and has no duty or obligation with respect to
    this CC0 or use of the Work.


================================================
FILE: README.md
================================================
<p align="center"><img src="images/how_they_devops.png"/></p>

> A curated collection of publicly available resources on how companies around the world practice DevOps

## Introduction

__How They DevOps__ is a curated knowledge repository on DevOps related topics - CI/CD

There are many ways to practice DevOps. Fortunately, many companies are willing to share how they do it. I believe there is much to learn from this documented use cases and published resources. The content you'll find in this repository is a list of such resources.

The reosurces are indexed by companies, technologies, years and DevOps related topics

Happy Learning!

*Please note, that all the resources mentioned here are publicly available resources.*

## By Company
<details>
  <summary>Adzuna</summary>

#### Articles
* [Continuous Integration and Continuous Delivery with BitBucket Pipelines — Part 1 - 2018](https://medium.com/adzuna-engineering/continuous-integration-and-continuous-delivery-with-bitbucket-pipelines-part-1-588d8254f0b3)
* [Continuous Integration and Continuous Delivery with BitBucket Pipelines — Part 2 - 2018](https://medium.com/adzuna-engineering/continuous-integration-and-continuous-delivery-with-bitbucket-pipelines-part-2-4d0ce7b63f2a)
</details>

<details>
  <summary>Airbnb</summary>

#### Podcasts
* [Continuous Delivery at Airbnb - 2019](https://devops.com/devops-chat-continuous-delivery-at-airbnb)
</details>

<details>
  <summary>Amazon</summary>

#### Articles
* [What is DevOps?](https://aws.amazon.com/devops/what-is-devops)
* [DevOps Resources](https://aws.amazon.com/devops/resources)

#### Blog
* [AWS DevOps Blog](https://aws.amazon.com/blogs/devops/)

</details>

<details>
  <summary>Atlassian</summary>

#### Articles
* [What is DevOps?](https://www.atlassian.com/devops)

#### Blogs
* [Atlassian DevOps Blog](https://www.atlassian.com/blog/devops)
* [DevOps Best Practices](https://www.atlassian.com/solutions/devops/best-practices)
</details>

<details>
  <summary>Carwow</summary>

#### Articles
* [Speeding up our deploys by ~35% - 2019](https://medium.com/carwow-product-engineering/speeding-up-our-heroku-deploys-by-35-percent-f9fa6f6cf404)
</details>

<details>
  <summary>Cinglevue</summary>

#### Articles
* [DevOps: How to build an efficient CI/CD pipeline - 2019](https://medium.com/developers-coffee/how-to-build-an-efficient-ci-cd-pipeline-b5738ad567c8)
</details>

<details>
  <summary>CloudBees</summary>

#### Articles
* [DevOps Best Practices: Opinionated Software That Drives a Successful DevOps Culture - 2021](https://www.cloudbees.com/blog/devops-best-practices)
* [8 DevOps Tools You Should Use for Opinionated, Cloud Native App Development - 2021](https://www.cloudbees.com/blog/devops-tools-cloud-native-development)
* [Continuous Verification, AKA Just Doing DevOps - 2020](https://www.cloudbees.com/blog/continuous-verification)

#### Blog
* [CloudBees Blog](https://www.cloudbees.com/blog)

</details>

<details>
  <summary>Codefresh</summary>

#### Articles
* [CI/CD Pipelines for Kubernetes Apps with Pulumi & Codefresh - 2021](https://codefresh.io/webinars/ci-cd-pipelines-kubernetes-apps-pulumi-codefresh)
* [Using Google Container Registry To Invoke Codefresh Pipelines - 2021](https://codefresh.io/continuous-integration/using-google-container-registry-invoke-codefresh-pipelines/)
* [What Is Zero Trust & How Do We Implement It to Run Secure CI/CD Workflows in Kubernetes? - 2021](https://codefresh.io/security-testing/codefresh-runner-overview)
* [Kubernetes Deployment Antipatterns – part 1 - 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-1)
* [Kubernetes Deployment Antipatterns – part 2 - 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-2)
* [Kubernetes Deployment Antipatterns – part 3 - 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-3)
#### Blogs
* [Codefresh blog](https://codefresh.io/blog)
</details>

<details>
  <summary>Facebook</summary>

#### Articles
* [Rapid release at massive scale](https://engineering.fb.com/2017/08/31/web/rapid-release-at-massive-scale)

#### Blog
* [Facebook Engineering Blog](https://engineering.fb.com)
</details>

<details>
  <summary>Grandcentrix</summary>

#### Articles
* [How we use Jenkins Pipeline to standardize our Continuous Integration - 2019](https://medium.com/grandcentrix/how-we-use-jenkins-pipeline-to-simplify-our-continuous-integration-4fb462b0c15c)
</details>

<details>
  <summary>Hootsuite</summary>

#### Articles
* [Jenkins, Kubernetes, and Hashicorp Vault - 2018](https://medium.com/hootsuite-engineering/jenkins-kubernetes-and-hashicorp-vault-c2011bd2d66c)
</details>

<details>
  <summary>Kalisio</summary>

#### Articles
* [Why We Stopped Using So-Called Best Practices in Our CI/CD Process - 2019](https://medium.com/better-programming/why-we-stopped-using-so-called-best-practices-in-our-ci-cd-process-2ff09811f633)
</details>

<details>
  <summary>Kitabisa</summary>

#### Articles
* [Our CI/CD Journey — from Monolith to Micro-Services - 2020](https://medium.com/@ardityawahyu/our-ci-cd-journey-from-monolith-to-micro-servives-9e6787dc7274)
</details>

<details>
  <summary>Lyft</summary>

#### Articles
* [Continuous Deployment at Lyft - 2022](https://eng.lyft.com/continuous-deployment-at-lyft-9b457314771a)
</details>

<details>
  <summary>Microsoft</summary>

#### Articles
* [What is DevOps?](https://docs.microsoft.com/en-us/azure/devops/learn/what-is-devops)

#### Blog
* [Azure DevOps Blog](https://devblogs.microsoft.com/devops)

</details>

<details>
  <summary>Netflix</summary>

#### Articles
* [Applying Netflix DevOps Patterns to Windows](https://netflixtechblog.com/applying-netflix-devops-patterns-to-windows-2a57f2dbbf79)
* [Lumen: Custom, Self-Service Dashboarding For Netflix](https://netflixtechblog.com/lumen-custom-self-service-dashboarding-for-netflix-8c56b541548c)
* [Netflix Cloud Security: Detecting Credential Compromise in AWS - 2018](https://netflixtechblog.com/netflix-cloud-security-detecting-credential-compromise-in-aws-9493d6fd373a)

#### Blog
* [DevOps Blog](https://netflixtechblog.com/tagged/devops)
</details>

<details>
  <summary>90 Seconds</summary>

#### Articles
* [Lessons learned with Gitlab Runner on Kubernetes - 2019](https://medium.com/90seconds/lessons-learned-with-gitlab-runner-on-kubernetes-d547c30ad5fb)
</details>

<details>
  <summary>Opendoor</summary>

#### Articles
* [How We Got To Continuous Deployment With Rails, CircleCI, and Heroku - 2017](https://medium.com/opendoor-labs/continuous-deployment-with-rails-circleci-and-heroku-314635d800c6)
</details>

<details>
  <summary>Oursky</summary>

#### Articles
* [Battle Tested: How We Built and Master Our CI/CD Pipeline - 2019](https://m.oursky.com/battle-tested-how-we-built-and-master-our-ci-cd-pipeline-2ce99c9b2fa4)
</details>

<details>
  <summary>Pixel Point</summary>

#### Articles
* [Tips and tricks for scalable CI/CD flow - 2018](https://medium.com/pixelpoint/tips-and-tricks-for-scalable-ci-cd-flow-5fa9dd457f22)
</details>

<details>
  <summary>Prismic</summary>

#### Articles
* [We deploy everyday and this is how!](https://medium.com/@prismicio/we-deploy-everyday-and-this-is-how-6a5fc8fb0e2e)
</details>

<details>
  <summary>Red Hat</summary>

#### Articles
* [Who is a DevOps Engineer?](https://www.redhat.com/en/topics/devops/devops-engineer)
* [What is DevOps?](https://www.redhat.com/en/topics/devops)
* [What is DevSecOps?](https://www.redhat.com/en/topics/devops/what-is-devsecops)
* [You call that DevSecOps? Why your DevSecOps practice may be falling short](https://www.redhat.com/en/blog/devsecops-reducing-risk-and-increasing-agility)
* [What is a CI/CD pipeline? - Red Hat](https://www.redhat.com/en/topics/devops/what-cicd-pipeline)

#### Books
* [Free - DevOps with OpenShift](https://developers.redhat.com/topics/devops)
</details>

<details>
  <summary>Riskified</summary>

#### Articles
* [How to Build a CI/CD Process That Deploys on Kubernetes and Focuses on Developer Independence](https://medium.com/riskified-technology/how-to-build-a-ci-cd-process-that-deploys-on-kubernetes-and-focuses-on-developer-independence-7dc4c20984a)

</details>

<details>
  <summary>Slack</summary>

#### Articles
* [How we use Terraform at Slack - 2022](https://slack.engineering/how-we-use-terraform-at-slack/)
* [Development Environments at Slack - 2020](https://slack.engineering/development-environments-at-slack/)
* [Deploys at Slack - 2020](https://slack.engineering/deploys-at-slack/)
</details>

<details>
  <summary>Trendyol</summary>

#### Articles
* [Dependency Check at CI/CD Pipeline - 2020](https://medium.com/trendyol-tech/dependency-check-at-ci-cd-pipeline-17020e15b391)
</details>

<details>
  <summary>Uber</summary>

#### Articles
* [Security at Speed: Modern Security and DevOps](https://medium.com/uber-security-privacy/speed-security-devops-7f3ee7e5a2ae)
* [Introducing Makisu: Uber’s Fast, Reliable Docker Image Builder for Apache Mesos and Kubernetes](https://eng.uber.com/makisu/)

#### Blog
* [Uber Engineering Blog](https://eng.uber.com)
</details>

<details>
  <summary>Verizon</summary>

#### Articles
* [How our CI/CD workflow provides a model for other CDNs - 2018](https://vzmediaplatform.medium.com/how-our-ci-cd-workflow-provides-a-model-for-other-cdns-65f9f765b32a)
</details>

<details>
  <summary>Wildlife Studios</summary>

#### Articles
* [How we improved our CI/CD pipelines over the years - 2020](https://medium.com/tech-at-wildlife-studios/how-we-built-a-ci-cd-that-makes-developers-happy-2222f02ab29)
</details>

<details>
  <summary>XETICS</summary>

#### Articles
* [Our story with Flutter and Gitlab-Ci - 2019](https://medium.com/@fezu54/our-story-with-flutter-and-gitlab-ci-26bd40c26155)
</details>

## By Technology

<details>
  <summary>CircleCI</summary>

#### Articles
* [How We Got To Continuous Deployment With Rails, CircleCI, and Heroku - Opendoor, 2017](https://medium.com/opendoor-labs/continuous-deployment-with-rails-circleci-and-heroku-314635d800c6)
* [Our CI/CD Journey — from Monolith to Micro-Services - Kitabisa, 2020](https://medium.com/@ardityawahyu/our-ci-cd-journey-from-monolith-to-micro-servives-9e6787dc7274)
</details>

<details>
  <summary>Codefresh</summary>

#### Articles
* [CI/CD Pipelines for Kubernetes Apps with Pulumi & Codefresh - Codefresh, 2021](https://codefresh.io/webinars/ci-cd-pipelines-kubernetes-apps-pulumi-codefresh)
* [Using Google Container Registry To Invoke Codefresh Pipelines - Codefresh, 2021](https://codefresh.io/continuous-integration/using-google-container-registry-invoke-codefresh-pipelines/)
</details>

<details>
  <summary>GitLab</summary>

#### Articles
* [Lessons learned with Gitlab Runner on Kubernetes - 90 seconds, 2019](https://medium.com/90seconds/lessons-learned-with-gitlab-runner-on-kubernetes-d547c30ad5fb)
* [How we improved our CI/CD pipelines over the years - Wildlife Studios, 2020](https://medium.com/tech-at-wildlife-studios/how-we-built-a-ci-cd-that-makes-developers-happy-2222f02ab29)
* [Our story with Flutter and Gitlab-Ci - XETICS, 2019](https://medium.com/@fezu54/our-story-with-flutter-and-gitlab-ci-26bd40c26155)
</details>

<details>
  <summary>Heroku</summary>

#### Articles
* [Speeding up our deploys by ~35% - Carwow, 2019](https://medium.com/carwow-product-engineering/speeding-up-our-heroku-deploys-by-35-percent-f9fa6f6cf404)
* [How We Got To Continuous Deployment With Rails, CircleCI, and Heroku - Opendoor, 2017](https://medium.com/opendoor-labs/continuous-deployment-with-rails-circleci-and-heroku-314635d800c6)
</details>

<details>
  <summary>Jenkins</summary>

#### Articles
* [How we use Jenkins Pipeline to standardize our Continuous Integration - Grandcentrix, 2019](https://medium.com/grandcentrix/how-we-use-jenkins-pipeline-to-simplify-our-continuous-integration-4fb462b0c15c)
* [Jenkins, Kubernetes, and Hashicorp Vault - 2018](https://medium.com/hootsuite-engineering/jenkins-kubernetes-and-hashicorp-vault-c2011bd2d66c)
</details>

<details>
  <summary>Kubernetes</summary>

#### Articles
* [Kubernetes Deployment Antipatterns – part 1 - Codefresh, 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-1)
* [Kubernetes Deployment Antipatterns – part 2 - Codefresh, 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-2)
* [Kubernetes Deployment Antipatterns – part 3 - Codefresh, 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-3)
* [How to Build a CI/CD Process That Deploys on Kubernetes and Focuses on Developer Independence](https://medium.com/riskified-technology/how-to-build-a-ci-cd-process-that-deploys-on-kubernetes-and-focuses-on-developer-independence-7dc4c20984a)
* [Introducing Makisu: Uber’s Fast, Reliable Docker Image Builder for Apache Mesos and Kubernetes - Uber](https://eng.uber.com/makisu/)
* [How we improved our CI/CD pipelines over the years - Wildlife Studios, 2020](https://medium.com/tech-at-wildlife-studios/how-we-built-a-ci-cd-that-makes-developers-happy-2222f02ab29)
* [Lessons learned with Gitlab Runner on Kubernetes - 90 seconds, 2019](https://medium.com/90seconds/lessons-learned-with-gitlab-runner-on-kubernetes-d547c30ad5fb)
* [Our CI/CD Journey — from Monolith to Micro-Services - Kitabisa, 2020](https://medium.com/@ardityawahyu/our-ci-cd-journey-from-monolith-to-micro-servives-9e6787dc7274)
* [Jenkins, Kubernetes, and Hashicorp Vault - 2018](https://medium.com/hootsuite-engineering/jenkins-kubernetes-and-hashicorp-vault-c2011bd2d66c)
</details>

<details>
  <summary>OpenShift</summary>

#### Books
* [Free - DevOps with OpenShift](https://developers.redhat.com/topics/devops)
</details>

<details>
  <summary>Packer</summary>

#### Articles
* [Applying Netflix DevOps Patterns to Windows](https://netflixtechblog.com/applying-netflix-devops-patterns-to-windows-2a57f2dbbf79)
</details>

<details>
  <summary>Rails</summary>

#### Articles
* [How We Got To Continuous Deployment With Rails, CircleCI, and Heroku - Opendoor, 2017](https://medium.com/opendoor-labs/continuous-deployment-with-rails-circleci-and-heroku-314635d800c6)
</details>

<details>
  <summary>Travis CI</summary>

#### Articles
* [Why We Stopped Using So-Called Best Practices in Our CI/CD Process - Kalisio, 2019](https://medium.com/better-programming/why-we-stopped-using-so-called-best-practices-in-our-ci-cd-process-2ff09811f633)
</details>

<details>
  <summary>Windows</summary>

#### Articles
* [Applying Netflix DevOps Patterns to Windows](https://netflixtechblog.com/applying-netflix-devops-patterns-to-windows-2a57f2dbbf79)
</details>

## By Category

<details>
  <summary>DevOps</summary>

#### Articles
* [What is DevOps? - Amazon](https://aws.amazon.com/devops/what-is-devops)
* [What is DevOps? - Atlassian](https://www.atlassian.com/devops)
* [What is DevOps? - Microsoft](https://docs.microsoft.com/en-us/azure/devops/learn/what-is-devops)
* [What is DevOps? - Red Hat](https://www.redhat.com/en/topics/devops)
* [DevOps Best Practices: Opinionated Software That Drives a Successful DevOps Culture - CloudBees, 2021](https://www.cloudbees.com/blog/devops-best-practices)
* [8 DevOps Tools You Should Use for Opinionated, Cloud Native App Development - CloudBees, 2021](https://www.cloudbees.com/blog/devops-tools-cloud-native-development)
* [Continuous Verification, AKA Just Doing DevOps - CloudBees, 2020](https://www.cloudbees.com/blog/continuous-verification)

</details>

<details>
  <summary>AWS</summary>

#### Articles
* [Netflix Cloud Security: Detecting Credential Compromise in AWS - 2018](https://netflixtechblog.com/netflix-cloud-security-detecting-credential-compromise-in-aws-9493d6fd373a)
</details>

<details>
  <summary>CI/CD</summary>

#### Articles - How companies practice and apply CI/CD
* [What Is Zero Trust & How Do We Implement It to Run Secure CI/CD Workflows in Kubernetes? - Codefresh, 2021](https://codefresh.io/security-testing/codefresh-runner-overview)
* [How to Build a CI/CD Process That Deploys on Kubernetes and Focuses on Developer Independence - Riskified, 2020](https://medium.com/riskified-technology/how-to-build-a-ci-cd-process-that-deploys-on-kubernetes-and-focuses-on-developer-independence-7dc4c20984a)
* [We deploy everyday and this is how! - Prismic, 2017](https://medium.com/@prismicio/we-deploy-everyday-and-this-is-how-6a5fc8fb0e2e)
* [Continuous Integration and Continuous Delivery with BitBucket Pipelines — Part 1 - Adzuna, 2018](https://medium.com/adzuna-engineering/continuous-integration-and-continuous-delivery-with-bitbucket-pipelines-part-1-588d8254f0b3)
* [Continuous Integration and Continuous Delivery with BitBucket Pipelines — Part 2 - Adzuna, 2018](https://medium.com/adzuna-engineering/continuous-integration-and-continuous-delivery-with-bitbucket-pipelines-part-2-4d0ce7b63f2a)
* [Continuous Delivery at Airbnb - 2019](https://devops.com/devops-chat-continuous-delivery-at-airbnb)
* [Battle Tested: How We Built and Master Our CI/CD Pipeline - Oursky, 2019](https://m.oursky.com/battle-tested-how-we-built-and-master-our-ci-cd-pipeline-2ce99c9b2fa4)
* [How we use Jenkins Pipeline to standardize our Continuous Integration - Grandcentrix, 2019](https://medium.com/grandcentrix/how-we-use-jenkins-pipeline-to-simplify-our-continuous-integration-4fb462b0c15c)
* [How We Got To Continuous Deployment With Rails, CircleCI, and Heroku - Opendoor, 2017](https://medium.com/opendoor-labs/continuous-deployment-with-rails-circleci-and-heroku-314635d800c6)
* [Why We Stopped Using So-Called Best Practices in Our CI/CD Process - Kalisio, 2019](https://medium.com/better-programming/why-we-stopped-using-so-called-best-practices-in-our-ci-cd-process-2ff09811f633)
* [How our CI/CD workflow provides a model for other CDNs - Verizon, 2018](https://vzmediaplatform.medium.com/how-our-ci-cd-workflow-provides-a-model-for-other-cdns-65f9f765b32a)
* [Lessons learned with Gitlab Runner on Kubernetes - 90 seconds, 2019](https://medium.com/90seconds/lessons-learned-with-gitlab-runner-on-kubernetes-d547c30ad5fb)
* [DevOps: How to build an efficient CI/CD pipeline - Cinglevue, 2019](https://medium.com/developers-coffee/how-to-build-an-efficient-ci-cd-pipeline-b5738ad567c8)
* [How we improved our CI/CD pipelines over the years - Wildlife Studios, 2020](https://medium.com/tech-at-wildlife-studios/how-we-built-a-ci-cd-that-makes-developers-happy-2222f02ab29)
* [Our CI/CD Journey — from Monolith to Micro-Services - Kitabisa, 2020](https://medium.com/@ardityawahyu/our-ci-cd-journey-from-monolith-to-micro-servives-9e6787dc7274)
* [Speeding up our deploys by ~35% - Carwow, 2019](https://medium.com/carwow-product-engineering/speeding-up-our-heroku-deploys-by-35-percent-f9fa6f6cf404)
* [Our story with Flutter and Gitlab-Ci - XETICS, 2019](https://medium.com/@fezu54/our-story-with-flutter-and-gitlab-ci-26bd40c26155)
* [Jenkins, Kubernetes, and Hashicorp Vault - 2018](https://medium.com/hootsuite-engineering/jenkins-kubernetes-and-hashicorp-vault-c2011bd2d66c)

#### Articles - Learn about CI/CD
* [What is a CI/CD pipeline? - Red Hat](https://www.redhat.com/en/topics/devops/what-cicd-pipeline)
* [Tips and tricks for scalable CI/CD flow - Pixel Point, 2018](https://medium.com/pixelpoint/tips-and-tricks-for-scalable-ci-cd-flow-5fa9dd457f22)

#### Articles - CI/CD with company products
* [CI/CD Pipelines for Kubernetes Apps with Pulumi & Codefresh - Codefresh, 2021](https://codefresh.io/webinars/ci-cd-pipelines-kubernetes-apps-pulumi-codefresh)
* [Using Google Container Registry To Invoke Codefresh Pipelines - Codefresh, 2021](https://codefresh.io/continuous-integration/using-google-container-registry-invoke-codefresh-pipelines/)

#### Books
* [Free - DevOps with OpenShift](https://developers.redhat.com/topics/devops)
</details>

<details>
  <summary>Dashboards</summary>

#### Articles
* [Lumen: Custom, Self-Service Dashboarding For Netflix](https://netflixtechblog.com/lumen-custom-self-service-dashboarding-for-netflix-8c56b541548c)
</details>

<details>
  <summary>DevSecOps</summary>

#### Articles
* [What is DevSecOps? - Red Hat](https://www.redhat.com/en/topics/devops/what-is-devsecops)
* [You call that DevSecOps? Why your DevSecOps practice may be falling short - Red Hat](https://www.redhat.com/en/blog/devsecops-reducing-risk-and-increasing-agility)
* [Security at Speed: Modern Security and DevOps - Uber, 2017](https://medium.com/uber-security-privacy/speed-security-devops-7f3ee7e5a2ae)
* [Netflix Cloud Security: Detecting Credential Compromise in AWS - Netflix, 2018](https://netflixtechblog.com/netflix-cloud-security-detecting-credential-compromise-in-aws-9493d6fd373a)
* [DevSecOps: Making Security Central To Your DevOps Pipeline - Spacelift](https://spacelift.io/blog/what-is-devsecops)
</details>

<details>
  <summary>Release</summary>

#### Articles
* [Rapid release at massive scale - Facebook, 2017](https://engineering.fb.com/2017/08/31/web/rapid-release-at-massive-scale)
</details>

## By Year

<details>
  <summary>2021</summary>

#### Articles
* [CI/CD Pipelines for Kubernetes Apps with Pulumi & Codefresh - Codefresh, 2021](https://codefresh.io/webinars/ci-cd-pipelines-kubernetes-apps-pulumi-codefresh)
* [Using Google Container Registry To Invoke Codefresh Pipelines - Codefresh, 2021](https://codefresh.io/continuous-integration/using-google-container-registry-invoke-codefresh-pipelines/)
* [What Is Zero Trust & How Do We Implement It to Run Secure CI/CD Workflows in Kubernetes? - Codefresh, 2021](https://codefresh.io/security-testing/codefresh-runner-overview)
* [Kubernetes Deployment Antipatterns – part 1 - Codefresh, 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-1)
* [Kubernetes Deployment Antipatterns – part 2 - Codefresh, 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-2)
* [Kubernetes Deployment Antipatterns – part 3 - Codefresh, 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-3)
* [DevOps Best Practices: Opinionated Software That Drives a Successful DevOps Culture - CloudBees](https://www.cloudbees.com/blog/devops-best-practices)
* [8 DevOps Tools You Should Use for Opinionated, Cloud Native App Development - CloudBees](https://www.cloudbees.com/blog/devops-tools-cloud-native-development)
</details>

<details>
  <summary>2020</summary>

#### Articles
* [Dependency Check at CI/CD Pipeline - Trendyol](https://medium.com/trendyol-tech/dependency-check-at-ci-cd-pipeline-17020e15b391)
* [How to Build a CI/CD Process That Deploys on Kubernetes and Focuses on Developer Independence - Riskified](https://medium.com/riskified-technology/how-to-build-a-ci-cd-process-that-deploys-on-kubernetes-and-focuses-on-developer-independence-7dc4c20984a)
* [Continuous Verification, AKA Just Doing DevOps - CloudBees](https://www.cloudbees.com/blog/continuous-verification)
* [How we improved our CI/CD pipelines over the years - Wildlife Studios, 2020](https://medium.com/tech-at-wildlife-studios/how-we-built-a-ci-cd-that-makes-developers-happy-2222f02ab29)
* [Our CI/CD Journey — from Monolith to Micro-Services - 2020](https://medium.com/@ardityawahyu/our-ci-cd-journey-from-monolith-to-micro-servives-9e6787dc7274)
</details>

<details>
  <summary>2019</summary>

#### Podcasts
* [Continuous Delivery at Airbnb](https://devops.com/devops-chat-continuous-delivery-at-airbnb)

#### Articles
* [Lessons learned with Gitlab Runner on Kubernetes - 90 seconds](https://medium.com/90seconds/lessons-learned-with-gitlab-runner-on-kubernetes-d547c30ad5fb)
* [DevOps: How to build an efficient CI/CD pipeline - Cinglevue](https://medium.com/developers-coffee/how-to-build-an-efficient-ci-cd-pipeline-b5738ad567c8)
* [Speeding up our deploys by ~35% - Carwow](https://medium.com/carwow-product-engineering/speeding-up-our-heroku-deploys-by-35-percent-f9fa6f6cf404)
* [Our story with Flutter and Gitlab-Ci - XETICS, 2019](https://medium.com/@fezu54/our-story-with-flutter-and-gitlab-ci-26bd40c26155)
</details>

<details>
  <summary>2018</summary>

#### Articles
* [Netflix Cloud Security: Detecting Credential Compromise in AWS - Netflix](https://netflixtechblog.com/netflix-cloud-security-detecting-credential-compromise-in-aws-9493d6fd373a)
* [Continuous Integration and Continuous Delivery with BitBucket Pipelines — Part 1 - Adzuna](https://medium.com/adzuna-engineering/continuous-integration-and-continuous-delivery-with-bitbucket-pipelines-part-1-588d8254f0b3)
* [Continuous Integration and Continuous Delivery with BitBucket Pipelines — Part 2 - Adzuna](https://medium.com/adzuna-engineering/continuous-integration-and-continuous-delivery-with-bitbucket-pipelines-part-2-4d0ce7b63f2a)
* [Tips and tricks for scalable CI/CD flow - Pixel Point](https://medium.com/pixelpoint/tips-and-tricks-for-scalable-ci-cd-flow-5fa9dd457f22)
* [How our CI/CD workflow provides a model for other CDNs - Verizon](https://vzmediaplatform.medium.com/how-our-ci-cd-workflow-provides-a-model-for-other-cdns-65f9f765b32a)
* [Jenkins, Kubernetes, and Hashicorp Vault - 2018](https://medium.com/hootsuite-engineering/jenkins-kubernetes-and-hashicorp-vault-c2011bd2d66c)
</details>

<details>
  <summary>2017</summary>

#### Articles
* [Rapid release at massive scale - Facebook](https://engineering.fb.com/2017/08/31/web/rapid-release-at-massive-scale)
* [Security at Speed: Modern Security and DevOps - Uber](https://medium.com/uber-security-privacy/speed-security-devops-7f3ee7e5a2ae)
* [We deploy everyday and this is how! - Prismic](https://medium.com/@prismicio/we-deploy-everyday-and-this-is-how-6a5fc8fb0e2e)
</details>

### More Infra & DevOps projects

<p align="center"><a href="https://github.com/bregman-arie/devops-exercises"><img src="images/devops_exercises.png"/></a></p>
<p align="center"><a href="https://github.com/bregman-arie/devops-resources"><img src="images/devops_resources.png"/></a></p>
<p align="center"><a href="https://github.com/bregman-arie/infraverse"><img src="images/infraverse.png"/></a></p>

### Credits
* Inspired by [Howtheytest](https://github.com/abhivaikar/howtheytest) from [Abhijeet Vaikar](https://github.com/abhivaikar)

### Contribute
Contributions welcome! Read the [contribution guidelines](contributing.md) first.

### License
[![CC0](https://mirrors.creativecommons.org/presskit/buttons/88x31/svg/cc-zero.svg)](https://creativecommons.org/publicdomain/zero/1.0)


================================================
FILE: code-of-conduct.md
================================================
# Contributor Covenant Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, gender identity and expression, level of experience,
nationality, personal appearance, race, religion, or sexual identity and
orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment
include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or
advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic
  address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a
  professional setting

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at upgundecha@gmail.com. All
complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The project team is
obligated to maintain confidentiality with regard to the reporter of an incident.
Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good
faith may face temporary or permanent repercussions as determined by other
members of the project's leadership.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
available at [http://contributor-covenant.org/version/1/4][version]

[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/


================================================
FILE: contributing.md
================================================
# Contribution Guidelines

Please note that this project is released with a
[Contributor Code of Conduct](code-of-conduct.md). By participating in this
project you agree to abide by its terms.

---
Please feel free to fork the repo and add blog posts, videos, incidents reports or any other useful resource to the repo.

You may find the [Markdown Link Generator](https://chrome.google.com/webstore/detail/markdown-link-generator/glnecdafikgonniihbdjneaikhcgcbhb?hl=en) extension for Google Chrome Browser easy to generate links in Markdown inline text link format. This tool will help to generate links for resources with minimal steps and context switching.

Ensure your pull request adheres to the following guidelines:

- Make sure the high level list is alphabetically ordered

Thank you for your suggestions!


## Updating your PR

A lot of times, making a PR adhere to the standards above can be difficult.
If the maintainers notice anything that we'd like changed, we'll ask you to
edit your PR before we merge it. There's no need to open a new PR, just edit
the existing one. If you're not sure how to do that,
[here is a guide](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md)
on the different ways you can update your PR so that we can merge it.
Download .txt
gitextract_atgcq_0b/

├── LICENSE
├── README.md
├── code-of-conduct.md
└── contributing.md
Condensed preview — 4 files, each showing path, character count, and a content snippet. Download the .json file or copy for the full structured content (39K chars).
[
  {
    "path": "LICENSE",
    "chars": 7048,
    "preview": "Creative Commons Legal Code\n\nCC0 1.0 Universal\n\n    CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE\n"
  },
  {
    "path": "README.md",
    "chars": 26366,
    "preview": "<p align=\"center\"><img src=\"images/how_they_devops.png\"/></p>\n\n> A curated collection of publicly available resources on"
  },
  {
    "path": "code-of-conduct.md",
    "chars": 3228,
    "preview": "# Contributor Covenant Code of Conduct\n\n## Our Pledge\n\nIn the interest of fostering an open and welcoming environment, w"
  },
  {
    "path": "contributing.md",
    "chars": 1296,
    "preview": "# Contribution Guidelines\n\nPlease note that this project is released with a\n[Contributor Code of Conduct](code-of-conduc"
  }
]

About this extraction

This page contains the full source code of the bregman-arie/howtheydevops GitHub repository, extracted and formatted as plain text for AI agents and large language models (LLMs). The extraction includes 4 files (37.0 KB), approximately 9.9k tokens. Use this with OpenClaw, Claude, ChatGPT, Cursor, Windsurf, or any other AI tool that accepts text input. You can copy the full output to your clipboard or download it as a .txt file.

Extracted by GitExtract — free GitHub repo to text converter for AI. Built by Nikandr Surkov.

Copied to clipboard!