InfoQ Homepage Continuous Integration Content on InfoQ
-
Continuous Delivery for (Smart) Trucks
Peter Thorngren, from Volvo Trucks, explains how the future world of smart trucks and autonomous transportation systems rely deeply on continuous delivery techniques like virtualization, test automation and continuous integration.
-
GitLab 8.5 Brings Improved Performance, Todos, and Geo-Replication
GitLab 8.5 brings a host of new features and improvements, including a significant performance boost, especially when running very large instances; Todos, a new feature aimed to help keep track of pending tasks for developers; and GitLab Geo, only available for GitLab Enterprise Edition, that supports geo-replication to improve performance for geographically distributed teams.
-
Crafting Quality Software
Tarcio Saraiva and Adam Crough talked about crafting quality software at the 1st Conference in Melbourne, Australia. InfoQ asked them to share their views on what software quality is, and to explain the business benefits and how it can be managed. InfoQ also asked them about the role for testing, how continuous integration supports quality, and advice for delivering high quality software products.
-
Measure and Improve Code Quality
InfoQ interviewed Boris Modylevsky about the importance of measuring code quality and how measurements can be used to improve quality, integrating static code analysis in continuous integration, testing coverage and test automation, and the benefits that continuous integration with integrated code analysis and test coverage can bring.
-
Apache Maven JDeps Plugin 3.0.0 Released
A new maven plugin that uses the jdeps utility to find uses of JDK Internal APIs has been released. When activated, the plugin will force a failure if the code uses any internal API. Internal APIs will be unaccessible as of Java 9, therefore this plugin helps developers adapt their code to the next version of Java. Despite being labeled as 3.0.0, this is the first release of the plugin.
-
More Feature Branching Means Less Continuous Integration
Many teams now implicitly discard continuous integration due to ever-easier feature branching and an under-appreciation of trunk based development says Steve Smith. InfoQ did an interview with him about different branching approaches and how they can be combined with continuous integration, and how using build feature branching can hamper continuous integration and continuous delivery.
-
Key Takeaways from the 'Agile on the Beach' Conference: Day One
At the fifth ‘Agile on the Beach’ conference, held in Cornwall, UK, several leading practitioners of agile software delivery presented the state-of-the-art and emerging trends within this domain. Key messages included the need for the more rigorous use of the scientific method throughout the software delivery lifecycle, and the benefits provided by applying agile principles to product development.
-
Puppet Labs: State of DevOps Report 2015
The Puppet Labs: State of DevOps Report 2015 shows the current DevOps trends in IT, comparing the high and low performers in terms of deployment success and stability, and observing the link between architecture and developer productivity.
-
Gradle 2.5 Does Continuous Builds
Gradle 2.5 has been announced this month including a number of incubating features, such as Continuous Builds, Dependency Substitution Rules, Progress Events, Google Tests, and others.
-
Docker's Testing Infrastructure
Jessie Frazelle, member of Docker's core team, is responsible for Docker's testing infrastructure. Frazelle described Docker's build workflows for both the master branch and pull requests as well as the various tools that are part of the testing infrastructure. Jenkins, Consul and nsq are all key components of the testing infrastructure, working together with Docker's custom tools.
-
Lessons on Building Continuous Delivery for Infrastructure
Lindsay Holmwood, Flapjack's creator, offers advice to enable fast, with quality, feedback loops and to support small, discrete changes. Holmwood asserts that to get quality feedback there are five main issues to think about: the CAP theorem; SLA definition; SLA validation; interfaces between services; data and infrastructure immutability.
-
Applying Continuous Integration at Thales Naval Systems
Continuous Integration can help to find integration issues earlier and to visualize the status of the build to all involved. Integration problems can be detected at build-time in stead of run-time during testing and teams can get immediate feedback on changes that they made and on the impact on components that are developed by other teams.
-
Multi-repository Development at Google
Oftentimes, complex software projects span across multiple repositories on account of external dependencies. This can be a challenge in itself, explains Google WebRTC engineer Patrik Höglund, who also described Google's approach to developing software that uses dozens of third-party libraries such as Chrome.
-
Adoption of SAFe at TomTom
InfoQ interviewed Hans Aerts, vice president software development and agile coach at TomTom, about why they decided to adopt SAFe and how it was introduced and used to simplify the organizational structure and stop doing projects, why they focus on throughput rather than output, how they modified SAFe for Custom Systems, and what using SAFe has brought TomTom.
-
Benefits of Continuous Testing
At Unruly teams have been applying eXtreme Programming (XP) since being founded in 2006. Teams take a test-first approach to developing code and invest in automated checks that can be run in live environments. InfoQ interviewed Rachel Davies about the importance of a continuous approach to testing, how this has evolved over the years and the business advantage that it delivers to Unruly.