FAQ

Should I use stoobly-agent scaffold or Makefile commands?

We recommend the Makefile commands. These often run the stoobly-agent scaffold commands with other prerequisite commands and optimal flags.

These also run the scaffold commands in a Docker container to ensure dependencies are consistent across runs.

Which Workflow to use?

See this section:

Gradually test changes in the Scaffold workflows

Which Workflow does my custom container service go in?

This depends on what use-case you want to use the service for.

If you want to mock requests, then you should add it to the "record" workflow first.

Then only add it to the "mock" and "test" workflows if you want unrecorded requests to go the service.

Which Docker network does my service go in?

There are 2 main Docker networks:

• app.ingress

• app.egress

Refer to the main guide which explains what the networks are for:

Adding Custom Container Services

How to run concurrent test workflows in CI?

Ideally your CI pipelines are running on isolated hosts, but often that isn't the case.

Use the "namespace" flag to your workflow run command to avoid Docker resource conflicts. A recommended namespace name is the git commit of the branch's HEAD.

Makefile command example:

make -f .stoobly/docker/Makefile test options="--namespace $(git rev-parse HEAD)"

Scaffold run command example:

stoobly-agent scaffold workflow up test --namespace $(git rev-parse HEAD)

What agent version of Scaffold am I running?

Run this command to output the Docker image version of your Scaffold:

$ cat .stoobly/docker/.Dockerfile.context | grep "FROM"

FROM stoobly/agent:1.6