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
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,...
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...
One common pattern for automated releases I have seen and used relies on Git
tags as the catalyst for a release process. The immutable nature of releases
and the immutable nature of tags can definitely go hand in hand, but up until
few months ago Jenkins Pipeline was not able to trigger effectively off of Git
In this post I want to briefly share how to use tags...
Meet the Jenkins community at FOSDEM 2021!