Using FAST in Concurrent CI/CD Workflows

Necessary data

The following values are used as examples in this document:

  • token_Qwe12345 as a token.
  • rec_1111 and rec_2222 as test records identifiers.

Several FAST nodes can be deployed to be used simultaneously in concurrent CI/CD workflow. These nodes share the same token and work with a single cloud FAST node.

This deployment scheme is applicable to FAST nodes that operate in both recording and testing modes.

To avoid conflicts during concurrent FAST nodes operation, the BUILD_ID environment variable is passed to each node's container. This variable serves the following purposes:

  1. It is used as an additional identifier for a test record that is created by a FAST node in recording mode.
  2. It allows determining which test record should be used by a test run that is created by a FAST node in testing mode (so the test run become tied to the test record).
  3. It identifies a certain CI/CD workflow.

The BUILD_ID environment variable can comprise any combination of letter and digits as its value.

Next, an example will be given on how to run two FAST nodes simultaneously: in recording mode first, then in testing mode. The approach described below is scalable (you can use so many nodes as you need, the number of nodes is not limited to two as in the example below) and is applicable to a real CI/CD workflow.

Running FAST Node in Recording Mode to Use in Concurrent CI/CD Workflows

Note on the examples

The examples below use the essential set of the environment variables, enough for a FAST node container to be up and operational. This is made for the sake of simplicity.

Run the following command to run the first FAST node container in recording mode:

docker run --rm --name fast-node-1 \    # This command run the fast-node-1 container
-e WALLARM_API_HOST=api.wallarm.com \   # Wallarm API server host (in this case the host is located in the european Wallarm cloud)
-e WALLARM_API_TOKEN='qwe_12345' \      # The token to connect to the cloud FAST node
-e CI_MODE=recording \                  # This node will operate in recording mode
-e BUILD_ID=1 \                         # The BUILD_ID value (it must differ from the another one for the concurrent pipeline)
-p 8080:8080 wallarm/fast               # The port mapping is done here. Also, the Docker image to use is specified here.

Run the following command to run the second FAST node container in recording mode to be used in the concurrent CI/CD workflow:

docker run --rm --name fast-node-2 \
-e WALLARM_API_HOST=api.wallarm.com \
-e WALLARM_API_TOKEN='qwe_12345' \      # The token value should be identical to the one used for the first FAST node
-e CI_MODE=recording \
-e BUILD_ID=2 \                         # The BUILD_ID value differs from the one used for the first FAST node in another CI/CD workflow.
-p 8000:8080 wallarm/fast

Note on the docker run commands

The aforementioned commands are supposed to be run on the same Docker host, so in addition to the different BUILD_ID values, these commands have distinct container names (fast-node-1 and fast-node-2) and target ports values (8080 and 8000).

If you run FAST node containers on separate Docker hosts, then the docker run commands may differ only in the BUILD_ID values.

After execution of these two commands, two FAST nodes will operate in recording mode using the same cloud FAST node, but the distinct test records will be created.

The CI/CD tool console output will be similar to the one described here.

When the test records are populated with all the necessary baseline requests, shut down the corresponding FAST nodes and spin up another nodes in testing mode.

Running FAST Node in Testing Mode to Use in Concurrent CI/CD Workflows

Let's assume that the rec_1111 and rec_2222 test records were prepared during the operation of the fast-node-1 and fast-node-2 FAST nodes in recording mode.

Then, to direct a FAST node fired up in testing mode to use the rec_1111 test record, pass the BUILD_ID=1 environment variable to the node container. Similarly, pass the BUILD_ID=2 environment variable to use the rec_2222 test record. Use the corresponding docker run commands below to run FAST nodes in testing mode.

Run the following command to run the first FAST node container in testing mode:

docker run --rm --name fast-node-1 \
-e WALLARM_API_HOST=api.wallarm.com \
-e WALLARM_API_TOKEN='qwe_12345' \
-e CI_MODE=testing \                    # This node will operate in testing mode
-e BUILD_ID=1 \                         # The `BUILD_ID=1` variable corresponds to the `rec_1111` test record
wallarm/fast

Run the following command to run the second FAST node container in recording mode to be used in the concurrent CI/CD workflow:

docker run --rm --name fast-node-2 \
-e WALLARM_API_HOST=api.wallarm.com \
-e WALLARM_API_TOKEN='qwe_12345' \
-e CI_MODE=testing \                    # This node will operate in testing mode
-e BUILD_ID=2 \                         # The `BUILD_ID=2` variable corresponds to the `rec_2222` test record
wallarm/fast

The CI/CD tool console output will be similar to the one described here.

As a result of passing corresponding values of the BUILD_ID environment variables to the FAST nodes, two test runs will begin to execute simultaneously, each working with the distinct test record.

So you can run a few FAST nodes for concurrent CI/CD workflows by specifying the BUILD_ID environment variable, without creating any conflict between the nodes (a newly created test run will not abort the execution of a running test run).

results matching ""

    No results matching ""