Skip to content

Commit

Permalink
chore: respect the Splunk
Browse files Browse the repository at this point in the history
  • Loading branch information
mkolasinski-splunk committed Jul 12, 2024
1 parent 256f9a5 commit dd1ce19
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions runbooks/addonfactory-workflow-addon-release-docker-images.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,12 +11,12 @@ Once there is new Splunk release, and [matrix](https://github.com/splunk/addonfa
- figure out what version of Splunk is needed (sha) using go/fetcher
- trigger [pipeline](https://cd.splunkdev.com/taautomation/ta-automation-docker-images/-/pipelines/new) 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
## 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](https://repo.splunkdev.net:443/artifactory/generic/splcore/builds/develop/)
- Docker image is built by [pipeline](https://cd.splunkdev.com/core-ee/docker-splunk-internal/-/pipelines/new) 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](https://repo.splunkdev.net/ui/repos/tree/General/docker/docker-splunk-internal/unreleased/splunk-redhat-9).
- 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](https://repo.splunkdev.net:443/artifactory/generic/splcore/builds/develop/)
- Docker image is built by [pipeline](https://cd.splunkdev.com/core-ee/docker-splunk-internal/-/pipelines/new) 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](https://repo.splunkdev.net/ui/repos/tree/General/docker/docker-splunk-internal/unreleased/splunk-redhat-9).
#### 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]
Expand Down

0 comments on commit dd1ce19

Please sign in to comment.