Currently, Jenkins builds and tests every PR generated. For a simple docs-only commit, this is not only an unnecessary use of resources, it adds time to the ability to propagate updates to the website.
This PR adds a check step into the Jenkins pipeline to check the source branch of a PR (and additionally any branch push, although docs/ is skipped in config already), and if it sees the docs/ prefix, it sets a variable that is then used to skip all remaining stages.
Additionally, it includes a github action that does a strict build on the docs, intended to fail on any error.
Currently, Jenkins builds and tests every PR generated. For a simple docs-only commit, this is not only an unnecessary use of resources, it adds time to the ability to propagate updates to the website.
This PR adds a check step into the Jenkins pipeline to check the source branch of a PR (and additionally any branch push, although docs/ is skipped in config already), and if it sees the docs/ prefix, it sets a variable that is then used to skip all remaining stages.
Additionally, it includes a github action that does a strict build on the docs, intended to fail on any error.