Add ugo tests

Signed-off-by: Natalie Arellano <[email protected]>

Author: Natalie Arellano

content/docs/extension-author-guide/create-extension/build-dockerfile.md

@@ -3,40 +3,59 @@ title="Generating a build.Dockerfile"
 weight=404
 +++
 
+<!-- test:suite=dockerfiles;weight=4 -->
+
 ### Examine `tree` extension
 
 #### detect
 
-`cat $workspace/samples/extensions/tree/bin/detect` - the extension always detects (because its exit code is `0`) and provides a dependency
-  called `tree` by writing to the build plan
+<!-- test:exec -->
+```bash
+cat $workspace/samples/extensions/tree/bin/detect
+```
+
+The extension always detects (because its exit code is `0`) and provides a dependency called `tree` by writing to the build plan.
 
 #### generate
 
-`cat $workspace/samples/extensions/tree/bin/generate` - the extension generates a `build.Dockerfile` that installs `tree` on the builder
-  image
+<!-- test:exec -->
+```bash
+cat $workspace/samples/extensions/tree/bin/generate
+```
+
+The extension generates a `build.Dockerfile` that installs `tree` on the builder image.
 
 ### Re-create our builder with `hello-extensions` updated to require `tree`
 
-1. Edit `$workspace/samples/buildpacks/hello-extensions/bin/detect` to uncomment the first set of lines that
-  output `[[requires]]` to the build plan
+Edit `$workspace/samples/buildpacks/hello-extensions/bin/detect` to uncomment the first set of lines that output `[[requires]]` to the build plan:
 
-2. Create the builder:
+<!-- test:exec -->
+```bash
+sed -i '' "10,11s/#//" $workspace/samples/buildpacks/hello-extensions/bin/detect
+```
+
+Re-create the builder:
 
+<!-- test:exec -->
 ```
 pack builder create $registry_namespace/extensions-builder \
   --config $workspace/samples/builders/alpine/builder.toml \
   --publish
 ```
 
-### Build the application image
+### Re-build the application image
 
+<!-- test:exec -->
 ```
 pack build hello-extensions \
   --builder $registry_namespace/extensions-builder \
-  --lifecycle-image $LIFECYCLE_IMAGE \
+  --network host \
+  --path $workspace/samples/apps/java-maven \
   --verbose
 ```
 
+Note that `--network host` is necessary when using `registry_namespace=localhost:5000`.
+
 You should see:
 
 ```
@@ -60,7 +79,9 @@ Successfully built image hello-extensions
 
 ### See the image fail to run
 
-`docker run hello-extensions`
+```
+docker run hello-extensions
+```
 
 You should see:
 

content/docs/extension-author-guide/create-extension/building-blocks-extension.md

@@ -3,9 +3,14 @@ title="Building blocks of a CNB Image Extension"
 weight=403
 +++
 
+<!-- test:suite=dockerfiles;weight=3 -->
+
 ### Examine `tree` extension
 
-`tree $workspace/samples/extensions/tree`
+<!-- test:exec -->
+```bash
+tree $workspace/samples/extensions/tree
+```
 
 (That's right, we're using the very tool we will later be installing!) You should see something akin to the following:
 

content/docs/extension-author-guide/create-extension/run-dockerfile.md

@@ -3,54 +3,79 @@ title="Generating a run.Dockerfile"
 weight=405
 +++
 
+<!-- test:suite=dockerfiles;weight=5 -->
+
 ### Examine `curl` extension
 
 #### detect
 
-`cat $workspace/samples/extensions/curl/bin/detect` - the extension always detects and provides a dependency
-  called `curl`
+<!-- test:exec -->
+```bash
+cat $workspace/samples/extensions/curl/bin/detect
+```
+
+The extension always detects (because its exit code is `0`) and provides a dependency called `curl`.
 
 #### generate
 
-`cat $workspace/samples/extensions/curl/bin/generate` - the extension generates a `run.Dockerfile` that switches the run image to
-  reference `run-image-curl`
+<!-- test:exec -->
+```bash
+cat $workspace/samples/extensions/curl/bin/generate
+```
+
+The extension generates a `run.Dockerfile` that switches the run image to reference `run-image-curl`.
 
 ### Build a run image for `curl` extension to use
 
-1. `cat $workspace/samples/stacks/alpine/run/curl.Dockerfile` - this is a simple Dockerfile that creates a CNB run image
-  from the `curl` base image by adding the required CNB user configuration and `io.buildpacks.stack.id` label
-   * The Dockerfile could come from anywhere, but we include it in the `stacks` directory for convenience
+<!-- test:exec -->
+```bash
+cat $workspace/samples/stacks/alpine/run/curl.Dockerfile
+```
+
+This is a simple Dockerfile that creates a CNB run image from the `curl` base image by adding the required CNB user configuration and `io.buildpacks.stack.id` label.
 
-2. Build the image:
+The Dockerfile could come from anywhere, but we include it in the `stacks` directory for convenience.
 
-```
+Build the run image:
+
+<!-- test:exec -->
+```bash
 docker build \
   --file $workspace/samples/stacks/alpine/run/curl.Dockerfile \
   --tag run-image-curl .
 ```
 
 ### Re-create our builder with `hello-extensions` updated to require `curl`
 
-1. Edit `$workspace/samples/buildpacks/hello-extensions/bin/detect` to uncomment the second set of lines that
-  output `[[requires]]` to the build plan
-
-2. Create the builder:
+Edit `$workspace/samples/buildpacks/hello-extensions/bin/detect` to uncomment the second set of lines that output `[[requires]]` to the build plan:
 
+<!-- test:exec -->
+```bash
+sed -i '' "14,15s/#//" $workspace/samples/buildpacks/hello-extensions/bin/detect
 ```
+
+Re-create the builder:
+
+<!-- test:exec -->
+```bash
 pack builder create $registry_namespace/extensions-builder \
   --config $workspace/samples/builders/alpine/builder.toml \
   --publish
 ```
 
-### Build the application image
+### Re-build the application image
 
-```
+<!-- test:exec -->
+```bash
 pack build hello-extensions \
   --builder $registry_namespace/extensions-builder \
-  --lifecycle-image $LIFECYCLE_IMAGE \
+  --path $workspace/samples/apps/java-maven \
+  --network host \
   --verbose
 ```
 
+Note that `--network host` is necessary when using `registry_namespace=localhost:5000`.
+
 You should see:
 
 ```
@@ -81,7 +106,10 @@ Successfully built image hello-extensions
 
 ### See the image run successfully
 
-`docker run hello-extensions`
+<!-- test:exec -->
+```bash
+docker run hello-extensions
+```
 
 You should see something akin to:
 

content/docs/extension-author-guide/create-extension/setup-local-environment.md

@@ -3,12 +3,17 @@ title="Set up your local environment"
 weight=401
 +++
 
+<!-- test:suite=dockerfiles;weight=1 -->
+
 Let's walk through a build that uses extensions, step by step. We will see an image extension that installs `curl` on
 the builder image, and switches the run image to an image that has `curl` installed.
 
 ### Ensure Docker is running
 
-`docker version`
+<!-- test:exec -->
+```bash
+docker version
+```
 
 If you see output similar to the following, you're good to go! Otherwise, start Docker and check again.
 
@@ -36,19 +41,35 @@ Server: Docker Engine - Community
 
 ### Setup workspace directory
 
-`workspace=<your preferred workspace directory>`
+<!-- test:exec -->
+```bash
+workspace=$PWD # or your preferred workspace directory
+```
 
 ### Ensure pack version supports image extensions
 
-`pack version` - should be at least `0.28.0`
+<!-- test:exec -->
+```bash
+pack version
+```
 
-### Clone the samples repo
+The version should be at least `0.28.0`
 
-`cd $workspace`
+### Enable experimental features in pack
 
-`git clone https://github.com/buildpacks/samples.git`
+<!-- test:exec -->
+```bash
+pack config experimental true
+```
+
+### Clone the samples repo
 
-`cd samples`
+<!-- test:exec -->
+```bash
+cd $workspace
+git clone https://github.com/buildpacks/samples.git
+cd samples
+```
 
 <!--+ if false +-->
 ---

content/docs/extension-author-guide/create-extension/why-dockerfiles.md

@@ -3,64 +3,75 @@ title="Why Dockerfiles"
 weight=402
 +++
 
+<!-- test:suite=dockerfiles;weight=2 -->
+
 Let's see a build that requires base image extension in order to succeed.
 
 ### Examine `hello-extensions` buildpack
 
 #### detect
 
-`cat $workspace/samples/buildpacks/hello-extensions/bin/detect` - the buildpack always detects (because its exit code is `0`)
-but doesn't require any dependencies (as the output build plan is empty)
+<!-- test:exec -->
+```bash
+cat $workspace/samples/buildpacks/hello-extensions/bin/detect
+```
+
+The buildpack always detects (because its exit code is `0`) but doesn't require any dependencies (as the output build plan is empty).
 
 #### build
 
-`cat $workspace/samples/buildpacks/hello-extensions/bin/build` - the buildpack tries to use `tree` during the build
-phase, and defines a launch process called `curl` that runs `curl --version` at runtime
+<!-- test:exec -->
+```bash
+cat $workspace/samples/buildpacks/hello-extensions/bin/build
+```
 
-### Create a builder with extensions and publish it
+The buildpack tries to use `tree` at build-time, and defines a launch process called `curl` that runs `curl --version` at runtime.
 
-1. Ensure experimental features are enabled: `pack config experimental true`
+### Create a builder with extensions and publish it
 
-2. Download the latest lifecycle tarball from the GitHub [release page](https://github.com/buildpacks/lifecycle/releases/tag/v0.15.1)
-   * For linux containers on x86 architectures: `wget https://github.com/buildpacks/lifecycle/releases/download/v0.15.1/lifecycle-v0.15.1+linux.x86-64.tgz`
+Ensure you are authenticated with an OCI registry: `docker login` should succeed
 
-3. Edit `$workspace/samples/builders/alpine/builder.toml` to add the following at the end of the file:
+For test purposes, you can launch a local unauthenticated registry:
 
-```
-[lifecycle]
-uri = <path to lifecycle tarball in previous step>
+<!-- test:exec -->
+```bash
+docker run -d --rm -p 5000:5000 registry:2
 ```
 
-4. Ensure you are authenticated with an OCI registry: `docker login` should succeed
+Set your preferred registry namespace (typically your username if using Docker Hub): `registry_namespace=<your preferred registry namespace>`
+* For now, it is necessary for the builder to be pushed to a registry for builds with image extensions to succeed
 
-5. Set your preferred registry namespace (typically your username): `registry_namespace=<your preferred registry namespace>`
-  * For now, it is necessary for the builder to be pushed to a registry for builds with image extensions to succeed
-
-6. Create the builder:
+If using a test registry:
 
+<!-- test:exec -->
+```bash
+registry_namespace=localhost:5000
 ```
+
+Create the builder:
+
+<!-- test:exec -->
+```bash
 pack builder create $registry_namespace/extensions-builder \
   --config $workspace/samples/builders/alpine/builder.toml \
   --publish
 ```
 
 ### Build the application image
 
-1. Ensure experimental features are enabled: `pack config experimental true`
-
-2. Set the lifecycle image for `pack` to use in the untrusted builder workflow (as the trusted workflow that uses
-   the `creator` is not currently supported): `LIFECYCLE_IMAGE=buildpacksio/lifecycle:0.15.1`
-
-3. Build the application image (note that the "source" directory is effectively ignored in our example):
+Run `pack build` (note that the "source" directory is effectively ignored in our example):
 
 ```
 pack build hello-extensions \
   --builder $registry_namespace/extensions-builder \
-  --lifecycle-image $LIFECYCLE_IMAGE \
+  --network host \
+  --path $workspace/samples/apps/java-maven \
   --pull-policy always \
   --verbose
 ```
 
+Note that `--network host` is necessary when using `registry_namespace=localhost:5000`.
+
 You should see:
 
 ```
@@ -81,9 +92,9 @@ You should see:
 What happened: our builder doesn't have `tree` installed, so the `hello-extensions` buildpack failed to build (as it
 tries to run `tree --version` in its `./bin/build` script).
 
-* Even though there is a `samples/tree` extension that passed detection (`pass: samples/[email protected]`), because
-  the `hello-extensions` buildpack didn't require `tree` in the build plan, the extension was omitted from the detected
-  group (`skip: samples/[email protected] provides unused tree`).
+Even though there is a `samples/tree` extension that passed detection (`pass: samples/[email protected]`), because
+the `hello-extensions` buildpack didn't require `tree` in the build plan, the extension was omitted from the detected
+group (`skip: samples/[email protected] provides unused tree`).
 
 Let's take a look at how the `samples/tree` extension installs `tree` on the builder image...