From d86505eab47a724897c2811c72412fdf239a2d65 Mon Sep 17 00:00:00 2001 From: Stefan Spieker Date: Fri, 1 Nov 2024 15:16:20 +0100 Subject: [PATCH 1/2] added short section about jcasc --- content/doc/developer/testing/index.adoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/doc/developer/testing/index.adoc b/content/doc/developer/testing/index.adoc index 5e07991299f8..f72452daf35f 100644 --- a/content/doc/developer/testing/index.adoc +++ b/content/doc/developer/testing/index.adoc @@ -567,6 +567,13 @@ public class MyTest { } ---- +=== Verifying compatibility with Configuration as Code (JCasC) + +The link:https://plugins.jenkins.io/configuration-as-code/[Configuration as Code plugin] is an opinionated way to configure Jenkins based on human-readable declarative configuration files. +Writing such a file should be feasible without being a Jenkins expert, just translating into code a configuration process one is used to executing in the web UI. +If the plugin should support JCasC, it should also test the compatability. +More details can be found at the link:https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/docs/PLUGINS.md[configuration-as-code-plugin documentation]. + == Increasing Tests Timeout The default timeout for Jenkins integration tests is 180 seconds. From 694c39055f966e422c3fec89e6cc5d7e463724ca Mon Sep 17 00:00:00 2001 From: Stefan Spieker Date: Fri, 1 Nov 2024 19:40:04 +0100 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Kevin Martens <99040580+kmartens27@users.noreply.github.com> --- content/doc/developer/testing/index.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/doc/developer/testing/index.adoc b/content/doc/developer/testing/index.adoc index f72452daf35f..285a861c2ae9 100644 --- a/content/doc/developer/testing/index.adoc +++ b/content/doc/developer/testing/index.adoc @@ -570,9 +570,9 @@ public class MyTest { === Verifying compatibility with Configuration as Code (JCasC) The link:https://plugins.jenkins.io/configuration-as-code/[Configuration as Code plugin] is an opinionated way to configure Jenkins based on human-readable declarative configuration files. -Writing such a file should be feasible without being a Jenkins expert, just translating into code a configuration process one is used to executing in the web UI. -If the plugin should support JCasC, it should also test the compatability. -More details can be found at the link:https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/docs/PLUGINS.md[configuration-as-code-plugin documentation]. +Writing such a file can be done without being a Jenkins expert by translating a configuration process one is familiar with executing in the web UI into code. +If the plugin supports JCasC, it also tests compatibility. +More details can be found in the link:https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/docs/PLUGINS.md[configuration-as-code-plugin documentation]. == Increasing Tests Timeout