This blog post is about our phase 3 progress on GitHub Checks API Project, you can find our previous blog posts for phase 1 and phase 2. At the end of this summer, the GSoC journey for GitHub Checks API Project comes to an end as well. In this blog post, I’ll show you our works during the last month: Pipeline Support Rerun Request Support Git SCM Support Documentation All the...

Since the beginning of the project, the core value which drove its progress was "To enhance the user experience for running Jenkins jobs by reducing the overall execution time". To achieve this goal, we laid out a path: Compare the two existing git implementations i.e CliGitAPIImpl and JGitAPIImpl using performance benchmarking Use the results to create a feature which would improve the overall performance of git plugin Also,...

The final phase for the External Fingerprint Storage Project has come to an end and to finish off, we release one more fingerprint storage plugin: the PostgreSQL Fingerprint Storage Plugin! This post highlights the progress made during phase-3. To understand what the project is about and the past progress, please refer to the phase-1 post and the phase-2 post. Introducing the PostgreSQL Fingerprint Storage Plugin Why PostgreSQL? There were several reasons why it...

Another great coding phase for GitHub Checks API Project ends! In this phase, we focused on consuming the checks API in two widely used plugins: Warnings NG Plugin Code Coverage API Plugin Besides the external usage, we have also split the general checks API from its GitHub implementation and released both of the plugins: Checks API Plugin GitHub Checks Plugin Coding Phase 2 Demo [starts from 25:20] Warning Checks The newly released Warnings...

The second phase of the Git Plugin Performance Improvement project has been great in terms of the progress we have achieved in implementing performance improvement insights derived from the phase one JMH micro-benchmark experiments. What we’ve learned so far in this project is that a git fetch is highly correlated to the size of the remote repository. In order to make fetch improvements in this plugin,...

As another great phase for the External Fingerprint Storage Project comes to an end, we summarise the work done during this phase in this blog post. It was an exciting and fruitful journey, just like the previous phase, and offered some great learning experience. To understand what the project is about and the past progress, please refer to the phase 1 blog post. New Stories Completed We targeted four stories in...

Git Plugin Performance Improvement is a Google Summer of Code 2020 project. It aims to improve the performance of the git plugin, which provides fundamental git functionalities. Internally, the plugin provides these functionalities using two implementations: command line git and JGit (pure java implementation). CLI git is the default implementation for the plugin, a user can switch to JGit if needed The project is divided into two parallel...

This blog post is about our coding phase 1 progress on GSoC project: GitHub Checks API Plugin. The GitHub Checks API is a highly customized way to integrate CI tools to make reports for pull-requests (PRs). It allows users to see CI reports on GitHub pages directly. Figure 1. GitHub Check Run Screenshot from GitHub Docs What’s more exciting is that it can leave annotations on specific lines...

Externalizing fingerprint storage for Jenkins is a Google Summer of Code 2020 project. We are working on building a pluggable storage engine for fingerprints (see JEP-226). File fingerprinting is a way to track which version of a file is being used by a job/build, making dependency tracking easy. The fingerprint engine of Jenkins can track usages of artifacts, credentials, files, etc. within the system. Currently,...

This article has been presented in an recorded online session during the Jenkins 2020 UI/UX Hackfest. For Jenkins a large number of plugins are available that visualize the results of a wide variety of build steps. There are plugins available to render the test results, the code coverage, the static analysis and so on. All of these plugins typically pick up the build results of a given build...