Tim AbellA small flurry of slightly obscure improvements to gitopolis
https://github.com/timabell/gitopolis/releases
Broken up into small releases because of #ContinuousDelivery from `main`
iX MagaziniX-Workshop: Deep Dive in Helm – Kubernetes-Anwendungen effizient verwalten
Lernen Sie praxisnah, wie Sie Kubernetes-Applikationen mit Helm in modernen Containerumgebungen effizient verwalten.
#Containerisierung #ContinuousDelivery #ContinuousIntegration #DevOps #IT #iXWorkshops #Kubernetes #OpenSource #news
heise DeveloperMastering GitOps: Praxiswissen von Argo-CD-Fallstricken bis OCI-Patterns
Die Online-Konferenz am 25. Juni präsentiert praxisrelevante GitOps-Themen rund um Platform Engineering, ArgoCD, den Flux Operator und Manifest-Pattern.
#ContinuousDelivery #InfrastructureasCode #IT #Kubernetes #news
iX-Workshop: Deep Dive in Helm – Kubernetes-Anwendungen effizient verwalten
Lernen Sie praxisnah, wie Sie Kubernetes-Applikationen mit Helm in modernen Containerumgebungen aktiv und effizient verwalten.
#Containerisierung #ContinuousDelivery #ContinuousIntegration #DevOps #IT #iXWorkshops #Kubernetes #OpenSource #news
c't Magazinc’t-Workshop: GitLab CI im Praxiseinsatz
GitLab CI/CD verstehen und anwenden: Der Workshop zeigt, wie Sie Pipelines für Builds, Tests und Deployments strukturieren und effizient im Team nutzen.
#ContinuousDelivery #ContinuousIntegration #Git #IT #Softwareentwicklung #news
anknfriendsGitOps revolutioniert die Art und Weise, wie wir Applikationen ausliefern. Durch die Verwendung von Git als Single Source of Truth für Konfigurationen und Automatisierung von Deployments erreichen wir verbesserte Sicherheit, Nachvollziehbarkeit und schnellere Release-Cycles. Ein Blick lohnt sich! #DevOps #GitOps #ContinuousDelivery
Otto Raskhttps://www.ottorask.com/blog/quality-by-a-thousand-cuts
#Refactoring #ContinuousIntegration #ContinuousDelivery #Software #Programming #SoftwareDevelopment #Quality
Quality by a thousand cuts — ottorask.com
Refactoring a codebase should be a continuous activity, even outside “regular feature development”. It should be painless, swift, and as automated as possible to refactor a single line of code and ship that change into production on its own. This approach requires continuous integration and continuous delivery, and will become nearly impossible with a pull request based workflow. Being able to ship miniscule commits multiple times an hour will allow you to enhance your codebase so much more than any quality-gate setup will. In software we should be able to improve quality with many more much smaller steps, hence achieving quality by a thousand cuts.
I've been writing this piece on and off for around five years now. I've rewritten it a bunch of times. I think it is okay to publish now.
https://www.ottorask.com/blog/pull-requests-quality-theater-with-questionable-results
#PullRequest #ContinuousIntegration #ContinuousDelivery #Software #SoftwareDevelopment #ProductDevelopment #ExtremeProgramming #PairProgramming #MobProgramming #Quality #QualityControl #QualityAssurance
Pull requests: quality theater with questionable results — ottorask.com
Does your organization prefer or maybe even force pull requests for reviewing and validating changes before integrating to a mainline? I have news for you: you’re engaged in quality theater and the only thing the PRs are doing for you is add cognitive load and delays while preventing you from finding better ways to ensure you’re shipping a quality product without delays.
LeanpubMeasuring Continuous Delivery
In this book, Steve Smith shows how to measure your Continuous Delivery journey, so you can understand how fast you're travelling and how fast you need to go.
Steve Fenton ➜In the second episode of #ContinuousDelivery Office Hours, we looked at how you keep your software deployable at all times. I wrote up some notes on the awkward silence, the manual testing problem, how to tackle older code, and why automation becomes living documentation.
https://octopus.com/blog/continuous-delivery-office-hours-e2
