matt-rickard.ghost.io
An Ideal CI/CD System
A good CI/CD system means developer productivity. What an ideal CI/CD system looks like today.
9 links about Continuous Integration/Delivery (CI/CD)
- Sorting: Newest links first
- Topic: Continuous Integration/Delivery (CI/CD)
- getdbt.com
dbt - Transforming data. Transforming teams.
dbt is a SQL-first transformation workflow that lets teams quickly and collaboratively deploy analytics code following software engineering best practices like modularity, portability, CI/CD, and documentation. Now anyone on the data team can safely contribute to production-grade data pipelines.
- minimumcd.org
Minimum Viable CD
A minimal definition of continuous delivery (CD) is required to improve the flow of delivery and achieve the outcomes above. While our contexts may be different, there are universal practices common in all.
- remix.run
Remix Stacks
In just a few minutes, we can get your app off the ground and ready to deploy all wired up with a CI/CD pipeline, connected database with a basic data model (via prisma), and even user authentication!
- metrojobb.se
Floskelälskande enterpriseutvecklare
Hos oss kommer du att ligga i framkant inom så kallad "continuous delivery" med driftsättningar varje månad!
- github.com
auchenberg/volkswagen
Detects when your tests are being run in a CI server, and makes them pass.
- blog.teamtreehouse.com
Why You Should Use Continuous Integration and Continuous Deployment
Having a bad development workflow will cost you a lot. It can make your senior engineers be productive like juniors, or even worse push them to leave the company. A great workflow can make push your good developers to be great and your best to be exceptional.
- jimmyjanlen.com
Continuous Delivery Unconf @ Spotify
För några dagar sedan faciliterade jag en Open Space Unconference på Spotify för Continuous Delivery guildet. Det blev en grym dag med många bra och väldigt givande diskussioner. Ett tjog intressanta initiativ projekt trillade dessutom ut i slutet av dagen.
- nerds.airbnb.com
Testing at Airbnb
We went from a handful of brittle tests to a large, resilient suite. We’ve gutted our continuous integration stack and reduced our build times from 1 hour to about 6 minutes, while simultaneously handling many times the number of builds. Most importantly, we’ve gone from an engineering culture in which most new code shipped without a single test, to one in which a proposed change without tests will quickly be called out and corrected. In short, we’ve not only become a team that believes in tests; we’ve become one that actually writes them.