From 4ce3b607334b89b16b1a4336696133c2e8e21f71 Mon Sep 17 00:00:00 2001 From: Oleg Nenashev Date: Thu, 18 Jan 2024 16:25:14 +0100 Subject: [PATCH 1/4] Move Day 07 to Day 21 --- 2024/day07.md | 47 ----------------------------------------------- 2024/day21.md | 48 ++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 48 insertions(+), 47 deletions(-) diff --git a/2024/day07.md b/2024/day07.md index ad72d05..8b13789 100644 --- a/2024/day07.md +++ b/2024/day07.md @@ -1,48 +1 @@ -# Day 7: Advanced Code Coverage with Jenkins, GitHub and API Mocking -Presentation by [Oleg Nenashev](https://linktr.ee/onenashev), -Jenkins core maintainer and community builder at WireMock - -**TL;DR:** I will talk about how modern Jenkins allows you to analyze -and improve code coverage with help of the new Coverage Plugin for Jenkins, -support for standard formats (Cobertura, JaCoCo, gcov, JUnit, etc.), -test parallelization, and GitHub Checks API. -We will also delve into increasing the integration test coverage with help of WireMock and Testcontainers. - -![Jenkins and GitHub Checks](./Images/day07-1.png) - -## Resources - -- Video: Coming Soon (January 07) -- Slides: Coming Soon (January 07) - -## Full Abstract - -In 2015-2018, I talked about how to use the Jenkins Pipeline and custom libraries to do advanced integration tests and analyze code coverage. -Coverage plugins were rather weak, and one needed some scripts and hacks to make it work, and to DIY for distributed testing. In 2021 the situation has changed significantly thanks to the Coverage and Checks API plugins. -Distributed integration testing also became easier thanks to better coverage collectors and integrations with API mocking tools. So, good time to be alive… and use Jenkins! - -![Jenkins and GitHub Checks](./Images/day07-2.png) - -We will talk about how modern Jenkins allows you to improve and analyze code coverage. -We will talk about unit and integration testing with WireMock, -the new Coverage Plugin, -support for standard formats (Cobertura, JaCoCo, gcov, JUnit, etc.), -parallelization for heavy integration tests and API mocking, and integration with GitHub Checks API. -How can you analyze code coverage in Jenkins and when do you need to create your own libraries? -And what’s the fuzz about Testcontainers and WireMock for integration testing? - -![Jenkins and GitHub Checks](./Images/day07-3.png) - -## References - -- [Jenkins Coverage Plugin](https://plugins.jenkins.io/coverage/) -- [GitHub Checks Plugin](https://plugins.jenkins.io/github-checks/) -- [WireMock](https://wiremock.org/) -- [Testcontainers](https://www.testcontainers.org/) -- Demo - Coming soon - -Contribute to open source projects: -[Jenkins](https://www.jenkins.io/participate), -[WireMock](https://wiremock.org/participate), -[Testcontainers](https://java.testcontainers.org/contributing/) diff --git a/2024/day21.md b/2024/day21.md index e69de29..ad72d05 100644 --- a/2024/day21.md +++ b/2024/day21.md @@ -0,0 +1,48 @@ +# Day 7: Advanced Code Coverage with Jenkins, GitHub and API Mocking + +Presentation by [Oleg Nenashev](https://linktr.ee/onenashev), +Jenkins core maintainer and community builder at WireMock + +**TL;DR:** I will talk about how modern Jenkins allows you to analyze +and improve code coverage with help of the new Coverage Plugin for Jenkins, +support for standard formats (Cobertura, JaCoCo, gcov, JUnit, etc.), +test parallelization, and GitHub Checks API. +We will also delve into increasing the integration test coverage with help of WireMock and Testcontainers. + +![Jenkins and GitHub Checks](./Images/day07-1.png) + +## Resources + +- Video: Coming Soon (January 07) +- Slides: Coming Soon (January 07) + +## Full Abstract + +In 2015-2018, I talked about how to use the Jenkins Pipeline and custom libraries to do advanced integration tests and analyze code coverage. +Coverage plugins were rather weak, and one needed some scripts and hacks to make it work, and to DIY for distributed testing. In 2021 the situation has changed significantly thanks to the Coverage and Checks API plugins. +Distributed integration testing also became easier thanks to better coverage collectors and integrations with API mocking tools. So, good time to be alive… and use Jenkins! + +![Jenkins and GitHub Checks](./Images/day07-2.png) + +We will talk about how modern Jenkins allows you to improve and analyze code coverage. +We will talk about unit and integration testing with WireMock, +the new Coverage Plugin, +support for standard formats (Cobertura, JaCoCo, gcov, JUnit, etc.), +parallelization for heavy integration tests and API mocking, and integration with GitHub Checks API. +How can you analyze code coverage in Jenkins and when do you need to create your own libraries? +And what’s the fuzz about Testcontainers and WireMock for integration testing? + +![Jenkins and GitHub Checks](./Images/day07-3.png) + +## References + +- [Jenkins Coverage Plugin](https://plugins.jenkins.io/coverage/) +- [GitHub Checks Plugin](https://plugins.jenkins.io/github-checks/) +- [WireMock](https://wiremock.org/) +- [Testcontainers](https://www.testcontainers.org/) +- Demo - Coming soon + +Contribute to open source projects: +[Jenkins](https://www.jenkins.io/participate), +[WireMock](https://wiremock.org/participate), +[Testcontainers](https://java.testcontainers.org/contributing/) From 29e7e81e612d9573b7c786a95a6f4f4253794abb Mon Sep 17 00:00:00 2001 From: Oleg Nenashev Date: Thu, 18 Jan 2024 16:29:38 +0100 Subject: [PATCH 2/4] Update Day 21 content and affiliations --- 2024/Images/{day07-1.png => day21-1.png} | Bin 2024/Images/{day07-2.png => day21-2.png} | Bin 2024/Images/{day07-3.png => day21-3.png} | Bin 2024/day21.md | 19 ++++++++++--------- 4 files changed, 10 insertions(+), 9 deletions(-) rename 2024/Images/{day07-1.png => day21-1.png} (100%) rename 2024/Images/{day07-2.png => day21-2.png} (100%) rename 2024/Images/{day07-3.png => day21-3.png} (100%) diff --git a/2024/Images/day07-1.png b/2024/Images/day21-1.png similarity index 100% rename from 2024/Images/day07-1.png rename to 2024/Images/day21-1.png diff --git a/2024/Images/day07-2.png b/2024/Images/day21-2.png similarity index 100% rename from 2024/Images/day07-2.png rename to 2024/Images/day21-2.png diff --git a/2024/Images/day07-3.png b/2024/Images/day21-3.png similarity index 100% rename from 2024/Images/day07-3.png rename to 2024/Images/day21-3.png diff --git a/2024/day21.md b/2024/day21.md index ad72d05..21558d5 100644 --- a/2024/day21.md +++ b/2024/day21.md @@ -1,20 +1,20 @@ -# Day 7: Advanced Code Coverage with Jenkins, GitHub and API Mocking +# Day 21: Advanced Code Coverage with Jenkins, GitHub and API Mocking Presentation by [Oleg Nenashev](https://linktr.ee/onenashev), -Jenkins core maintainer and community builder at WireMock +Jenkins core maintainer, developer advocate and community builder at Gradle -**TL;DR:** I will talk about how modern Jenkins allows you to analyze +**TL;DR:** I will talk about how modern Jenkins allows you to analyze and improve code coverage with help of the new Coverage Plugin for Jenkins, -support for standard formats (Cobertura, JaCoCo, gcov, JUnit, etc.), +support for standard formats (Cobertura, JaCoCo, gcov, JUnit, etc.), test parallelization, and GitHub Checks API. We will also delve into increasing the integration test coverage with help of WireMock and Testcontainers. -![Jenkins and GitHub Checks](./Images/day07-1.png) +![Jenkins and GitHub Checks](./Images/day21-1.png) ## Resources -- Video: Coming Soon (January 07) -- Slides: Coming Soon (January 07) +- Video: Coming Soon (January 21) +- [Slides](https://speakerdeck.com/onenashev/advanced-code-coverage-with-jenkins-github-and-api-mocking/) (Premier - January 21) ## Full Abstract @@ -22,7 +22,7 @@ In 2015-2018, I talked about how to use the Jenkins Pipeline and custom librarie Coverage plugins were rather weak, and one needed some scripts and hacks to make it work, and to DIY for distributed testing. In 2021 the situation has changed significantly thanks to the Coverage and Checks API plugins. Distributed integration testing also became easier thanks to better coverage collectors and integrations with API mocking tools. So, good time to be alive… and use Jenkins! -![Jenkins and GitHub Checks](./Images/day07-2.png) +![Jenkins and GitHub Checks](./Images/day21-2.png) We will talk about how modern Jenkins allows you to improve and analyze code coverage. We will talk about unit and integration testing with WireMock, @@ -32,7 +32,7 @@ parallelization for heavy integration tests and API mocking, and integration wit How can you analyze code coverage in Jenkins and when do you need to create your own libraries? And what’s the fuzz about Testcontainers and WireMock for integration testing? -![Jenkins and GitHub Checks](./Images/day07-3.png) +![Jenkins and GitHub Checks](./Images/day21-3.png) ## References @@ -46,3 +46,4 @@ Contribute to open source projects: [Jenkins](https://www.jenkins.io/participate), [WireMock](https://wiremock.org/participate), [Testcontainers](https://java.testcontainers.org/contributing/) +[Gradle](https://gradle.org/resources/) From f595ecfd5a6d898c635d64527706bc3483e66d74 Mon Sep 17 00:00:00 2001 From: Oleg Nenashev Date: Fri, 26 Jan 2024 10:07:51 +0100 Subject: [PATCH 3/4] Adapt Day 21 to 26 --- 2024/Images/{day21-1.png => day26-1.png} | Bin 2024/Images/{day21-2.png => day26-2.png} | Bin 2024/Images/{day21-3.png => day26-3.png} | Bin 2024/day21.md | 49 ----------------------- 2024/day26.md | 49 +++++++++++++++++++++++ 5 files changed, 49 insertions(+), 49 deletions(-) rename 2024/Images/{day21-1.png => day26-1.png} (100%) rename 2024/Images/{day21-2.png => day26-2.png} (100%) rename 2024/Images/{day21-3.png => day26-3.png} (100%) diff --git a/2024/Images/day21-1.png b/2024/Images/day26-1.png similarity index 100% rename from 2024/Images/day21-1.png rename to 2024/Images/day26-1.png diff --git a/2024/Images/day21-2.png b/2024/Images/day26-2.png similarity index 100% rename from 2024/Images/day21-2.png rename to 2024/Images/day26-2.png diff --git a/2024/Images/day21-3.png b/2024/Images/day26-3.png similarity index 100% rename from 2024/Images/day21-3.png rename to 2024/Images/day26-3.png diff --git a/2024/day21.md b/2024/day21.md index 21558d5..e69de29 100644 --- a/2024/day21.md +++ b/2024/day21.md @@ -1,49 +0,0 @@ -# Day 21: Advanced Code Coverage with Jenkins, GitHub and API Mocking - -Presentation by [Oleg Nenashev](https://linktr.ee/onenashev), -Jenkins core maintainer, developer advocate and community builder at Gradle - -**TL;DR:** I will talk about how modern Jenkins allows you to analyze -and improve code coverage with help of the new Coverage Plugin for Jenkins, -support for standard formats (Cobertura, JaCoCo, gcov, JUnit, etc.), -test parallelization, and GitHub Checks API. -We will also delve into increasing the integration test coverage with help of WireMock and Testcontainers. - -![Jenkins and GitHub Checks](./Images/day21-1.png) - -## Resources - -- Video: Coming Soon (January 21) -- [Slides](https://speakerdeck.com/onenashev/advanced-code-coverage-with-jenkins-github-and-api-mocking/) (Premier - January 21) - -## Full Abstract - -In 2015-2018, I talked about how to use the Jenkins Pipeline and custom libraries to do advanced integration tests and analyze code coverage. -Coverage plugins were rather weak, and one needed some scripts and hacks to make it work, and to DIY for distributed testing. In 2021 the situation has changed significantly thanks to the Coverage and Checks API plugins. -Distributed integration testing also became easier thanks to better coverage collectors and integrations with API mocking tools. So, good time to be alive… and use Jenkins! - -![Jenkins and GitHub Checks](./Images/day21-2.png) - -We will talk about how modern Jenkins allows you to improve and analyze code coverage. -We will talk about unit and integration testing with WireMock, -the new Coverage Plugin, -support for standard formats (Cobertura, JaCoCo, gcov, JUnit, etc.), -parallelization for heavy integration tests and API mocking, and integration with GitHub Checks API. -How can you analyze code coverage in Jenkins and when do you need to create your own libraries? -And what’s the fuzz about Testcontainers and WireMock for integration testing? - -![Jenkins and GitHub Checks](./Images/day21-3.png) - -## References - -- [Jenkins Coverage Plugin](https://plugins.jenkins.io/coverage/) -- [GitHub Checks Plugin](https://plugins.jenkins.io/github-checks/) -- [WireMock](https://wiremock.org/) -- [Testcontainers](https://www.testcontainers.org/) -- Demo - Coming soon - -Contribute to open source projects: -[Jenkins](https://www.jenkins.io/participate), -[WireMock](https://wiremock.org/participate), -[Testcontainers](https://java.testcontainers.org/contributing/) -[Gradle](https://gradle.org/resources/) diff --git a/2024/day26.md b/2024/day26.md index e69de29..21558d5 100644 --- a/2024/day26.md +++ b/2024/day26.md @@ -0,0 +1,49 @@ +# Day 21: Advanced Code Coverage with Jenkins, GitHub and API Mocking + +Presentation by [Oleg Nenashev](https://linktr.ee/onenashev), +Jenkins core maintainer, developer advocate and community builder at Gradle + +**TL;DR:** I will talk about how modern Jenkins allows you to analyze +and improve code coverage with help of the new Coverage Plugin for Jenkins, +support for standard formats (Cobertura, JaCoCo, gcov, JUnit, etc.), +test parallelization, and GitHub Checks API. +We will also delve into increasing the integration test coverage with help of WireMock and Testcontainers. + +![Jenkins and GitHub Checks](./Images/day21-1.png) + +## Resources + +- Video: Coming Soon (January 21) +- [Slides](https://speakerdeck.com/onenashev/advanced-code-coverage-with-jenkins-github-and-api-mocking/) (Premier - January 21) + +## Full Abstract + +In 2015-2018, I talked about how to use the Jenkins Pipeline and custom libraries to do advanced integration tests and analyze code coverage. +Coverage plugins were rather weak, and one needed some scripts and hacks to make it work, and to DIY for distributed testing. In 2021 the situation has changed significantly thanks to the Coverage and Checks API plugins. +Distributed integration testing also became easier thanks to better coverage collectors and integrations with API mocking tools. So, good time to be alive… and use Jenkins! + +![Jenkins and GitHub Checks](./Images/day21-2.png) + +We will talk about how modern Jenkins allows you to improve and analyze code coverage. +We will talk about unit and integration testing with WireMock, +the new Coverage Plugin, +support for standard formats (Cobertura, JaCoCo, gcov, JUnit, etc.), +parallelization for heavy integration tests and API mocking, and integration with GitHub Checks API. +How can you analyze code coverage in Jenkins and when do you need to create your own libraries? +And what’s the fuzz about Testcontainers and WireMock for integration testing? + +![Jenkins and GitHub Checks](./Images/day21-3.png) + +## References + +- [Jenkins Coverage Plugin](https://plugins.jenkins.io/coverage/) +- [GitHub Checks Plugin](https://plugins.jenkins.io/github-checks/) +- [WireMock](https://wiremock.org/) +- [Testcontainers](https://www.testcontainers.org/) +- Demo - Coming soon + +Contribute to open source projects: +[Jenkins](https://www.jenkins.io/participate), +[WireMock](https://wiremock.org/participate), +[Testcontainers](https://java.testcontainers.org/contributing/) +[Gradle](https://gradle.org/resources/) From d560b67cff4d0156434726d789ef727b64486cab Mon Sep 17 00:00:00 2001 From: Oleg Nenashev Date: Fri, 26 Jan 2024 10:34:05 +0100 Subject: [PATCH 4/4] Uodate the list --- 2024.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/2024.md b/2024.md index e57ff3a..9b6b002 100644 --- a/2024.md +++ b/2024.md @@ -47,7 +47,7 @@ Or contact us via Twitter, my handle is [@MichaelCade1](https://twitter.com/Mich - [ ][ ] ♾️ 23 > [SQL Server 2022 on Linux Containers and Kubernetes from Zero to a Hero!](2024/day23.md) - Yitzhak David - [ ][✔️] ♾️ 24 > [DevSecOps - Defined, Explained & Explored](2024/day24.md) - Sameer Paradkar - [ ][✔️] ♾️ 25 > [Kube-Nation: Exploring the Land of Kubernetes](2024/day25.md) - Siddhant Khisty & Aakansha Priya -- [ ][ ] ♾️ 26 > [](2024/day26.md) +- [ ][✔️] ♾️ 26 > [Advanced Code Coverage with Jenkins and API Mocking](2024/day26.md) - Oleg Nenashev - [ ][ ] ♾️ 27 > [From Automated to Automatic - Event-Driven Infrastructure Management with Ansible](2024/day27.md) - Daniel Bodky - [ ][ ] ♾️ 28 > [Policy-as-Code Super-Powers! Rethinking Modern IaC With Service Mesh And CNI](2024/day28.md) - Kat Morgan & Marino Wijay - [ ][ ] ♾️ 29 > [The Reverse Technology Thrust](2024/day29.md) - Rom Adams @@ -124,7 +124,6 @@ Or contact us via Twitter, my handle is [@MichaelCade1](https://twitter.com/Mich - Saving Cloud Costs Using Existing Prometheus Metrics - Pavan Gudiwada - Code, Connect, and Conquer: Mastering Personal Branding for Developers - Pavan Belagatti - Mastering AWS OpenSearch: Terraform Provisioning and Cost Efficiency Series - Ranjini Ganeshan -- Advanced Code Coverage with Jenkins and API Mocking - Oleg Nenashev - GitOps: The next Frontier in DevOps! - Megha Kadur - Container Security for Enterprise Kubernetes environments - Imran Roshan - Navigating Cloud-Native DevOps: Strategies for Seamless Deployment - Yhorby Matias