Discover and read the best of Twitter Threads about #continuousintegration
Most recents (6)
Dealing with "Coupling" is one of the things that makes SW a genuinely difficult activity. But I think Coupling is at least as big a deal for SW dev teams as it is for the software itself.
Here's a #Thread
1/14
Here's a #Thread
1/14
Coupling is an interesting idea, and there are many dimensions to it. I particularly like the @mtnygard model of coupling described in this video, and have been quoting it for years.
2/14
2/14
At its roots the management of coupling is, I think, one of the deep fundamentals of design. Skill in this is what differentiates great SW design, from average or poor design to a large degree.
3/14
3/14
A #DevOps Engineer follows the entire software development cycle, from beginning to deployment and beyond. They use tools like version control systems, Infrastructure as a Code Service, and cloud computing services to improve efficiency and reliability. #software #engineering
DevOps Engineers use tools like Jenkins and Docker to automate the software development and deployment process, ensuring that updates and new features are delivered quickly and consistently. #DevOps #automation #continuousintegration
In the modern era, microservices architecture and container tools like Docker and Kubernetes are crucial for deploying and managing applications. DevOps Engineers must be skilled in these tools to effectively maintain systems. #DevOps #microservices #containers
#TDD, #CodeReview and #ContinuousIntegration in action - here is how with @marcandsweep we develop new features in #JaCoCo (jacoco.org/jacoco/):
as an example let's have a look at github.com/jacoco/jacoco/… …
as an example let's have a look at github.com/jacoco/jacoco/… …
… first we add high level "validation" test to study desired behavior, this test targets Records (openjdk.java.net/jeps/359) that are #JDK14 Preview Feature (openjdk.java.net/jeps/12),
so build fails locally, but only on JDK14 …
so build fails locally, but only on JDK14 …
… yes - locally for development we have many #Java versions installed … 
#ContinuousIntegration Pro-tip (of course I mean single branch):
Start adopting the expand-contract pattern.
Start adopting the expand-contract pattern.
Expand-contract is what blue-green deployments do.
You expand by installing a new version of the app, and then you contract by removing the old version.
You expand by installing a new version of the app, and then you contract by removing the old version.
Expand-contract is also heavily used for zero-down time database schema changes.
Let’s say you need to rename a table column.
You expand by adding a new column with the new name.
Feed the new column with data.
Once the app uses the new column, contract by removing the old one.
Let’s say you need to rename a table column.
You expand by adding a new column with the new name.
Feed the new column with data.
Once the app uses the new column, contract by removing the old one.
All of you #recruiting #fullstack developers, or calling yourselves #fullstack #software #developers, this is the stack. I call #shenanigans.
#UI & #UX
#Accessibility
#Internationalization
#GraphicDesign
#Javascript
WAF and client-side #security
Client-facing #performancetesting
Caching & #CDN
#APIDesign
Identity management
#Microservices
#Database access patterns
#ContinuousIntegration
Build servers (#Jenkins)
#Accessibility
#Internationalization
#GraphicDesign
#Javascript
WAF and client-side #security
Client-facing #performancetesting
Caching & #CDN
#APIDesign
Identity management
#Microservices
#Database access patterns
#ContinuousIntegration
Build servers (#Jenkins)
Source code management
Deployment methodologies
#ConfigurationManagement
#InfrastructureAsCode
Infrastructure Security
#TDD
Concurrent programming
Backend performance testing
#Monitoring
Alerting
Storage subsystems
Messaging subsytems
#Networking
Deployment methodologies
#ConfigurationManagement
#InfrastructureAsCode
Infrastructure Security
#TDD
Concurrent programming
Backend performance testing
#Monitoring
Alerting
Storage subsystems
Messaging subsytems
#Networking
Hi @InfoQ, your #GitFlow article is flat out wrong. It is 100% incompatible with #ContinuousIntegration and #ContinuousDelivery. continuousdeliveryconsulting.com/blog/organisat… / @danielbryantuk
Here's an @InfoQ article I did in 2015, explaining why #GitFlow is incompatible with CI let alone CD infoq.com/news/2015/10/b…
Here's an @InfoQ video of a talk I did in 2015, which includes an explanation of why #GitFlow is incompatible with CI infoq.com/presentations/…
