Continuous integration consolidation (#1711)

* Consolidate continuous integration documentation

* Exclude plone.restapi installed stuff from docs

Author: stevepiercy

docs/_inc/_continuous-integration.md

@@ -0,0 +1,7 @@
+Plone project repositories use {term}`continuous integration` (CI) to run tests, ensure code quality, or provide previews for every contribution.
+Plone uses GitHub workflows, Jenkins, Cypress, Read the Docs, and other services for CI.
+All of a project's CI jobs must pass before a contribution may be accepted.
+
+```{seealso}
+{doc}`/contributing/core/continuous-integration`
+```

docs/conf.py

@@ -125,15 +125,21 @@
     "**/CONTRIBUTORS.rst",
     "**/LICENSE.rst",
     "**/README.rst",
+    "**/eggs",
+    "_inc/.*",
     "plone.restapi/.*",
     "plone.restapi/bin",
+    "plone.restapi/develop-eggs",
     "plone.restapi/docs/source/glossary.md",  # There can be only one Glossary.
+    "plone.restapi/eggs",
     "plone.restapi/ideas",
     "plone.restapi/include",
     "plone.restapi/lib",
     "plone.restapi/news",
+    "plone.restapi/parts",
     "plone.restapi/performance",
     "plone.restapi/src",
+    "plone.restapi/var",
     "volto/contributing/branch-policy.md",
     "volto/contributing/install-docker.md",
     "volto/contributing/install-git.md",

docs/contributing/core/continuous-integration.md

@@ -27,6 +27,12 @@ Otherwise GitHub workflows do not run automatically, and require a member with w
 GitHub workflows should pass before running Jenkins checks and before merging an open pull request.
 
 
+## `mr-roboto`
+
+[`mr-roboto`](https://github.com/plone/mr.roboto) enforces the requirement of a signed Plone Contributor Agreement from a new contributor, and being assigned to a Plone team on GitHub.
+It also suggests to run Jenkins for many Plone packages.
+
+
 ## Jenkins
 
 [Jenkins](https://jenkins.plone.org) is the authoritative source to see whether the complete test suite passes for any Plone version under development.

docs/contributing/core/index.md

@@ -292,14 +292,10 @@ This enables automatic closing of the related issue when the pull request is mer
 This also creates a hyperlink to the original issue for easy reference.
 
 
-## Jenkins and mr.roboto
+## Continuous integration
 
-Plone has a continuous integration ({term}`CI`) setup and follows CI rules.
-
-When you push a change to a Plone package, there may be GitHub workflows that run automatically.
-The CI package [mr.roboto](https://github.com/plone/mr.roboto) will perform some checks and suggest that you run Jenkins after all other CI runs.
-
-See {doc}`continuous-integration` for more information.
+```{include} /_inc/_continuous-integration.md
+```
 
 
 ## Additional material

docs/contributing/index.md

@@ -60,13 +60,13 @@ All contributors to the Plone Documentation follow the Code of Conduct.
 
 First-time contributors should read and follow our guide {doc}`first-time`.
 
+
 (contributing-continuous-integration-label)=
 
 ## Continuous integration
 
-Plone project repositories use continuous integration (CI) to run tests, ensure code quality, or provide previews for every contribution.
-Plone uses GitHub Actions, Jenkins, Cypress, Netlify, and other services for CI.
-All of a project's CI jobs must pass before a contribution may be accepted.
+```{include} /_inc/_continuous-integration.md
+```
 
 (contributing-change-log-label)=
 

docs/glossary.md

@@ -756,6 +756,8 @@ Load balancer
 CI
 continuous integration
     Continuous integration (CI) is the practice of integrating all your code changes into the main branch of a shared source code repository early and often, automatically testing each change when you commit or merge them, and automatically kicking off a build.
+    
+    Read about Plone's {doc}`/contributing/core/continuous-integration`.
 
 CD
 continuous deployment