FAQ

Should I use CLI 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 does my custom container service go in?

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

If you want to record 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 two Docker networks:

• app.ingress

• app.egress

To learn more:

Scaffold

How to run concurrent test workflows in CI?

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

Add 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. Also set the Makefile option workflow_up_extra_options="--no-publish" so Docker ports are not published in CI.

Note: Namespaces are only supported by test workflows and custom workflows based on the test workflow template. Record and mock workflows do not support namespaces.

Makefile command example:

make -f .stoobly/services/Makefile test workflow_up_extra_options="--no-publish" options="--namespace $(git rev-parse HEAD)"

Scaffold run command example:

stoobly-agent scaffold workflow up test --no-publish --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/services/.Dockerfile.context | grep "FROM"

FROM stoobly/agent:2.0