Hi all, I am pleased to announce that I have published the v0.4.0 of the Gerrit Code Review plugin for Jenkins (see [1]) with the official support of the Gerrit Checks plugin (see [2]). It will show up in a few hours in the Jenkins plugin central and will then be available for download.
Thanks to Thomas Draebing (SAP) and David Ostrovsky for adding the support and reviewing it. I am pleased to announce that Thomas has been added to the list of the maintainers of the project. The Gerrit Checks plugin allows to control and display the results of the CI/CD pipeline directly from the change screen. For instance, if you open [3] and click on the “Checks” tab, you will see: - latest CI/CD status for the change - Deep-link to the logs - Action to re-run the build - Live status of the build — * — See below a short list of Q&As on the topic: Q1: What are the minimum requirements for using Gerrit Checks? You need Gerrit v3.1.0 and the Checks plugin installed. On the Jenkins side, you need the gerrit-code-review plugin v0.4.0 and a multi-branch pipeline configured to point to the Gerrit project. Q2: What are the benefits of using Gerrit Checks compared to the Gerrit Trigger plugin? Gerrit Checks doesn’t require any stream events configuration or SSH channel active between Jenkins and Gerrit. Also, allows to track in Gerrit the status of the build, without having to “pollute” the change log with lots of comments and links coming from the Jenkins job. Q3: Is Gerrit Checks a mandatory requirement for using the Gerrit Code Review plugin in Jenkins? No, it can be enabled only if you wish to use the Checks plugin in Gerrit. Otherwise, the Gerrit Code Review plugin will work exactly as before. Q4: Where can I find a more detailed set of instructions on how to use Checks and Jenkins together? I am planning to write a blog-post later this week on https://gitenterprise.me with a short video with detailed step-by-step instructions on how to use them together with GerritHub.io. Q5: What is the performance of Checks compared with the standard multi-branch pipeline? Checks is incredibly fast compared to the regular branch scanning: it allows to skip altogether the expensive refs advertisement of all open changes and just focus on those ones that need verification. Q6: Does the Gerrit Code Review plugin comes with Enterprise Support? The Gerrit Code Review plugin is OpenSource under the Apache 2.0 license, like any other plugin for Jenkins. If you need Enterprise Support, you can Google ‘Gerrit Enterprise Support’ and you can find companies that would be happy to give you commercial support for using it in production with guaranteed SLAs and 24x7. — * — Last but not least, thanks again Thomas and David for this amazing achievement. Luca. [1] https://plugins.jenkins.io/gerrit-code-review [2] https://github.com/jenkinsci/gerrit-code-review-plugin#integrating-with-the-gerrit-checks-plugin [3] https://gerrit-review.googlesource.com/c/gerrit/+/249336 -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/07F39FEB-FF99-4325-8E45-9D6AF33B8DA9%40gmail.com.
