Hi. I'm getting this error when trying to run first build in the "Validate Jenkins" chapter of the Templating Engine tutorial:

[JTE] Obtained Pipeline Template from job configuration
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in /var/jenkins_home/workspace/validate
[Pipeline] {
[Pipeline] isUnix
[Pipeline] sh

• docker inspect -f . maven

The command 'docker' could not be found in this WSL 2 distro.
We recommend to activate the WSL integration in Docker Desktop settings.

See https://docs.docker.com/docker-for-windows/wsl/ for details.

[Pipeline] isUnix
[Pipeline] sh

• docker pull maven

The command 'docker' could not be found in this WSL 2 distro.
We recommend to activate the WSL integration in Docker Desktop settings.

See https://docs.docker.com/docker-for-windows/wsl/ for details.

[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 1
Finished: FAILURE

I'm having various wsl distros, even wsl1 and wsl2. But my default wsl distro is setting to one wsl2 valid one (in fact, the jenkins where i'm running the tutorial is executing in a docker container launched from that wsl2 distro -Ubuntu-20.04 for reference-.

The link in this sentence doesn't take me anywhere, "You can read more about how to externalize library configuration here."

It would be very helpful to have a learning lab that walks through how to containerize Jenkins and set it up so that the instance comes up preconfigured using:

Plugin Installation: installed during container build time
Jenkins Server Configs: configured using Jenkins Configuration as Code (JCasC)
Job Configurations: Created using Job DSL and invoked from the JCasC file
Everything Else: for things that can’t be easily configured using Job DSL or JCasC, use System Groovy Scripts invoked from JCasC

This learning lab should show how to take the upstream Jenkins community image and customize it for use with SDP:

1. Show how to manually configure a Jenkins instance (plugin installs, instance configs, job configs)
2. Show how to automate that manual configuration by extending the community container image with the strategies outlined above

I noticed that when deploying the docs locally the JTE docs weren't updating properly. The only file in pages/jte/docs/pages was installation.rst, while the folders like Governance and Library Templating were missing. This was after running make docs, make live, and make get-remote-docs

I think it has to do with Git being reluctant to update the local Head if doing so would overwrite local changes. One solution that seemed to work for me is to update line 34 of the make file (and maybe line 30, too), changing git checkout master to git checkout remotes/origin/HEAD (or maybe remotes/origin/master) so that the update comes from the remote repository, and not the local copy.

@steven-terrana does that sound good?

I'm in the process of investigating a bug of Jenkins template engine and am building a SSCCE for use case. I stumbled over The 'local development' section of the docs which describes the setup of a test Jenkins which requires a lot of manual configuration and provides a UI which is of no use for the case a simple reproducer for a bug.

It'd be nice to have instructions and a ready docker container for a one liner which allows to test the local pipeline and prints the job logs from a mounted volume.

"thesesteps"

https://boozallen.github.io/sdp-docs/learning-labs/1/jte-advanced-features/3-pipeline-lifecycle-hooks.html

Should read: "Learn the different types of jobs available in Jenkins and when to use them"