Pascal Herms, Author at XABLU https://www.xablu.com/author/pherms/ We build Ventures, Products and Teams Wed, 19 Nov 2025 12:01:21 +0000 en-US hourly 1 https://wordpress.org/?v=7.0.2 https://www.xablu.com/wp-content/uploads/2019/08/xablu-favicon-100x100.png Pascal Herms, Author at XABLU https://www.xablu.com/author/pherms/ 32 32 SonarQube: adding Pull Request for cleaner and safer code https://www.xablu.com/2021/09/10/sonarqube-adding-pull-request-decoration/ Fri, 10 Sep 2021 16:22:53 +0000 https://www.xablu.com/?p=15039 Sonarqube is an open-source platform which performs a continuous code analysis to help your team write cleaner and safer code. You can view this report of your code in your […]

The post SonarQube: adding Pull Request for cleaner and safer code appeared first on XABLU.

]]>

Sonarqube is an open-source platform which performs a continuous code analysis to help your team write cleaner and safer code. You can view this report of your code in your SonarQube account, where you can see possible bugs, security issues, code smells and other suggestions to avoid technical debt. However, it is also possible to add this report straight into your ALM’s provider’s interface!  

Let’s take a look at PR Decoration with SonarQube. 

This feature (available with the developer edition of SonarQube), allows you to add SonarQube analysis and a Quality Gate to your Pull Requests on GitHub, Bitbucket, Azure DevOps and GitLab. 

By introducing this continuous analysis directly to your source code location, you can support your team to detect bugs quicker. The team will also be supported to write cleaner code to prevent technical debt and a legacy codebase. When submitting a pull request, possible security issues are directly identified. Moreover, any unit tests that are build into your code can also be included in the report, to provide a complete overview of your code analysis. Clean up your code directly after submitting your PR: the code eventually published to production, and coming into the hands of your end-users, will be double checked and more reliable.  

The PR decoration can be built directly into your CI/CD workflow: every time a Pull Request is send, the analysis can automatically be executed. It takes some work to build the PR Decoration properly, but it has a lot of benefits when it is in place.  

Are you interested in learning more about SonarQube and PR Decorations, or do you need help to implement this within your project? Get in touch to discuss how we can help you improve your code quality workflow.   

The post SonarQube: adding Pull Request for cleaner and safer code appeared first on XABLU.

]]> How automating your build-test-deploy process helps your team https://www.xablu.com/2021/09/01/jenkins-to-increase-teams-efficiency/ Wed, 01 Sep 2021 13:40:34 +0000 https://www.xablu.com/?p=14969 Within any (mobile) team, we always analyse our efficiency: how many story points did we complete, how many errors or bugs are returned and how quickly can we bring new features to […]

The post How automating your build-test-deploy process helps your team appeared first on XABLU.

]]>

Within any (mobile) team, we always analyse our efficiency: how many story points did we complete, how many errors or bugs are returned and how quickly can we bring new features to our customers?  

There are many things that have an effect on our efficiency. For example, good and proactive communication at the beginning will lead to less frustration and more complete deliverables. The efficiency of a team is also highly reliant on the processes the team has in place: clear and solid processes can support the team and increase their efficiency. This is where DevOps plays a vital role. DevOps (combination of Software Development and IT Operations) is aimed at continuous delivery with high quality software. Basically, it means there are automatic processes in place that help the team of developers to continuously deliver their work which has been tested and deemed of high enough quality. In practice, builds will be automated, tested and deployed. 

This process can be automated, meaning the process will be accurate, thorough and supportive throughout the development lifecycle. 

One tool you can use to automate the build-test-deploy process is called Jenkins: within this tool it is possible to set up pipelines. With pipelines, you can have different environments for different purposes: you can have a development pipeline solely for the developers to work in, an alpha pipeline for quality assurance officers, a beta pipeline for specific users who can test the first versions and a production pipeline that is meant for all the users. This is an example of a pipeline structure: the app will have to go through all the phases before the users will receive the updates, meaning the code will be tested thoroughly and bugs can be fixed before users receive the newest updates.

How does this specifically increase your team’s efficiency? Bugs will be found and solved prior to moving the app to production, manual deployment is not necessary anymore and a level of code quality can be warranted. A good DevOps process, such as the one you can create through Jenkins, requires time and energy to make sure it is solid, but the effort will be well-paid back by an increase in efficiency.  

Want to learn how you can automate the build-deployment process for your project using Jenkins? Follow our training! 

The post How automating your build-test-deploy process helps your team appeared first on XABLU.

]]>