Introduce ability to shuffle AB Test spaces

[Jakeii]

What does this change?

Add a configuration to shuffle the AB test audience spaces so that when tests are allocated, they are not allocated linearly from 0->999, but randomly.

A super simple way to do this is to store the desired order for each space in an array and lookup the mvtid to use. Using a straight random number each time would be

Why?

The current allocation setup:

Hopefully this demonstrates the issue, that tests are allocate to spaces linearly, this causes tests variants overlap, something we have been conscious of as of late, especially with the addition of more test spaces.

This could cause tests to influence each other.

With shuffling:

[github-actions]

Deploy build 30379 of dotcom:rendering-all to CODE

All deployment options

• Deploy build 30379 of dotcom:rendering-all to CODE
• Deploy parts of build 30379 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[github-actions]

Deploy build 2779 of dotcom:ab-testing to CODE

All deployment options

• Deploy build 2779 of dotcom:ab-testing to CODE
• Deploy parts of build 2779 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[github-actions]

🚀 Image pushed to AWS ECR

Image digest: sha256:e3237a8097fe7a98488189ba558751700a80633cc543a88775cbf9ac9407bc48

🐛 Run the image locally

The following can be used to run the image locally:

# Refer to image using the immutable digest. Find alternatives below.
IMAGE_IDENTIFIER="@sha256:e3237a8097fe7a98488189ba558751700a80633cc543a88775cbf9ac9407bc48"

# Refer to image using branch tag
# IMAGE_IDENTIFIER=":branch-jlk-ab-test-shuffle"

# Refer to image using build tag
# IMAGE_IDENTIFIER=":build-30379"

# Refer to image via the GitHub commit SHA tag
# IMAGE_IDENTIFIER=":sha-66023162144ae2515b242aa8f3d0e095f53cb3ca"

# Set environment variables for the AWS CLI
AWS_PROFILE="<A_PROFILE_FROM_JANUS>"
AWS_DEFAULT_REGION="eu-west-1"

IMAGE_ACCOUNT_ID=$(aws ssm get-parameter --name /organisation/accounts/deployTools --query "Parameter.Value" --output text)
REGISTRY="${IMAGE_ACCOUNT_ID}.dkr.ecr.${AWS_DEFAULT_REGION}.amazonaws.com"
IMAGE="${REGISTRY}/guardian/dotcom-rendering${IMAGE_IDENTIFIER}"

# Login to AWS ECR https://docs.aws.amazon.com/AmazonECR/latest/userguide/registry_auth.html
aws ecr get-login-password | docker login --username AWS --password-stdin $REGISTRY

# Pull the image
docker pull $IMAGE

# Run the image. You'll likely need to set additional flags. See https://docs.docker.com/reference/cli/docker/container/run.
docker run $IMAGE

---

From guardian/actions-publish-image.