Tag Archives: Continuous Integration

Some years ago I write a blog post about how to generate test reports in SonarQube separate in test report for unit tests and for integration tests. Since SonarQube 6.2 the test report isn’t separate in these categories any more (see SonarQube’s blog post). SonarQube merges all test reports to one test report with an overall coverage. So how to ...

Most pipelines require secrets to authenticate with some external resources.All secrets should live outside of our code repository and should be fed directly into the pipeline. Jenkins offers a credentials store where we can keep our secrets and access them in a couple of different ways. Why dump credentials Jenkins is an easy pick when it comes to intelligence gathering. ...

The official documentation for Jenkins Shared Libraries is pretty good, but not perfect. This article expands on how to use Jenkins Shared Libraries with private git repositories, semantically version, and unit test your libraries and provides working examples which you can run yourself. Short Intro Jenkins Shared Library is a handy tool when dealing with multiple similar pipelines. If you ...

Basics of setting up a Jenkins multibranch pipeline job and defining a Jenkinsfile. Creating Multibranch Pipeline Job If you want to follow this article but don’t have a Jenkins instance at hand you can use my GitHub project to spin up a dockerized Jenkins: git clone https://github.com/hoto/jenkinsfile-examples.git cd jenkinsfile-examples docker-compose pull docker-compose up Let’s open Jenkins by going to localhost:8080 ...

Setting the stage For the last two years I’ve worked on a Node.js project. We used GitHub for source management and Jenkins for continuous integration. We also had a deployment tool based on Docker and Terraform. We have done a few improvements to the configuration during this time. One of the changes that had a positive impact was to run ...

Continuous integration (CI) can seem like a waste of time or added work that does not push features forward. But when you think about your project’s “health” and how you foresee future processes working with other developers, it leaves an underlining issue. Processes need to be automated to save us time! In the last few years, continuous integration and deployment ...

Overcome the challenge of maintaining code quality in a CI/CD workflow with Continuous Reliability CI/CD practices encourage frequent code integration in development, speed up preparations for new releases and automate deployments. And with this new tooling, these parts of the software development lifecycle have all improved and accelerated. At the same time, the data that we use to evaluate the ...

Successful teams know that CI/CD isn’t enough. With things breaking faster than ever, many are adding Continuous Reliability to their workflows. Most engineering teams have adopted an agile development practice and are pushing for shorter and faster release cycles. The difficulties associated with more frequent deployments to production, not to mention evergrowing code bases, led to the rise of Continuous ...

Discover faster, more efficient performance monitoring with an enterprise APM product learning from your apps. Take the AppDynamics APM Guided Tour! In DevOps, Continuous Integration (CI) is increasingly the integration method of choice, in large part because of the speed at which it enables the release of new features, bug fixes, and product update. In a digital world that moves ...