addonfactory-workflow-addon-release-docker-images.md

Runbook to creating and publishing docker images used in reusable workflow

Runbook to publish multiple images of different Linux flavors and versions for scripted inputs tests

Once there is new Splunk release, and matrix is updated, we need to make sure that Splunk images for scripted inputs tests are created and published.

Steps

Update OS images

• check what OSs are listed in definition of matrix for scripted inputs tests here
• if any is missing in ta-automation-docker-images then add new Dockerfile

Create images and publish them to ECR

• figure out what version of Splunk is needed (sha) using BUILD field from splunk_matrix (alternatively use go/fetcher)
• trigger pipeline for every OS flavor separately

Runbook to publish unreleased Splunk image for testing

Whenever there is a need for running tests with unreleased splunk, we need to create relevant Splunk docker image and publish it to aws ecr

Steps

Build docker image and publish to artifactory

• Prior creating docker image it needs to be determined which revision of core Splunk repo is required. Splunk docker images are based on Splunk builds published to artifactory by CI in core repository. Their names match SHA of the commit in core repo: develop builds artifactory
• Docker image is built by pipeline which required UNRELEASED_SPLUNK_SHA as an input variable - provide first 12 characters of desired revision on Splunk core repo. Once image is built, it is published to artifactory.

Pull built image locally, tag and publish to ecr

• okta-artifactory-login -t docker
• docker pull docker.repo.splunkdev.net/docker-splunk-internal/unreleased/splunk-redhat-9:[image-tag]
• docker tag docker.repo.splunkdev.net/docker-splunk-internal/unreleased/splunk-redhat-9:[image-tag] "956110764581.dkr.ecr.us-west-2.amazonaws.com/splunk/splunk:[new-image-tag]"
• set AWS environment variables: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN
• aws ecr get-login-password --region us-west-2 | docker login --username AWS --password-stdin 956110764581.dkr.ecr.us-west-2.amazonaws.com
• docker push 956110764581.dkr.ecr.us-west-2.amazonaws.com/splunk/splunk:[new-image-tag]
• confirm that image is visible in AWS ECR
• there are TAs which use Splunk images with installed java fot testing (e.g. JBOSS). Separate image with installed java has to be built, tagged and pushed to ECR. This branch can be used for this purpose. Existing CI/CD expects Splunk image with tag "956110764581.dkr.ecr.us-west-2.amazonaws.com/splunk/splunk:[new-image-tag]-java"