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.
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.
Takari, the Maven-focused company started by Maven founder Jason van Zyl, announced that Maven Central is now mirrored on Google Cloud Storage. Maven Central is the central repository where many open source Java libraries publish their artifacts.
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.
Bazel, the build system that Google open sourced six months ago, has reached the first beta milestone as planned, adding support for several languages and technologies.
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.
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 has been announced this month including a number of incubating features, such as Continuous Builds, Dependency Substitution Rules, Progress Events, Google Tests, and others.
Jessie Frazzelle, member of Docker's core team, is responsible for Docker's testing infrastructure. Frazzelle 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.
Last week, RedHat hosted a "Microservices Architecture Developer Day" in London, and presented a set of technologies and patterns that can be used to create microservice-based applications using open-source solutions like Kubernetes, Docker, Fabric8 and Maven. Read on for more details about the day, including links to the presentations and demo videos.
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.
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.
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.
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.
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.
CONTENT IN THIS BOX PROVIDED BY OUR SPONSOR
Blog Series: A skeptic's guide to Continuous Delivery