In this blogpost, we will show you how to provision a Jenkins VM and setup a CI/CD pipeline to connect a code repository in Apache Subversion (SVN) and deploy the application into a Tomcat service.
A few months ago, we announced a preview of the Open Service Broker for Azure (OSBA), the simplest way to connect applications running in cloud native environments, like Kubernetes, Cloud Foundry, and OpenShift, to the rich suite of managed services available in Azure.
With DevOps World | Jenkins World around the corner (September 16-19 in San Francisco) and the recent announcement of Azure DevOps, this seems like a good time to provide an update on the options for working with Jenkins on Microsoft Azure.
Note: for its 1-year anniversary, I refreshed this blog article in November 2019 to leverage new features with Helm 3 and Azure Pipelines (mainly YAML for both Build/CI and Release/CD), as well as to incorporate great feedback we’ve been receiving from our readers.
The service mesh may sound complex, but at its heart, it’s a very simple idea: a set of network proxies that transparently run alongside microservices, implementing reliability, observability, and security features by measuring and manipulating inter-service (“east-west”) traffic.
In recent years, many developers have discovered the power of distributed tracing for debugging regressions and performance issues in their backend systems, especially for those of us with complex microservices architectures.