Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: upgrade tests #35

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dkaras-splunk
Copy link
Contributor

@dkaras-splunk dkaras-splunk commented Nov 27, 2024

TA-> TA Upgrade implementation ADDON-73792

This pull request introduces a new feature to our CI/CD pipeline, focusing on automating upgrade testing for Technology Add-ons (TA). The goal is to streamline the release process by incorporating scalable and user-friendly solutions capable of executing upgrade scenarios

Key Features:
Automated Upgrade Testing: Introduces jobs for upgrade testing within the GitHub CI/CD pipeline.

Flexible Version Testing: Allows users to provide multiple TA versions on which upgrade tests should be executed. In this repo, ta_upgrade_version parameter is responsible for passing the info about versions being tested. Also, both GitHub and Splunkbase releases are supported, depending on the format of the version string provided:

vX.X.X - for GitHub releases
X.X.X - for Splunkbase releases
additionally, latest can be passed to use the latest version from GitHub
example run - https://github.com/splunk/splunk-add-on-for-amazon-web-services/actions/runs/12045945177

Part of
https://github.com/splunk/ta-automation-app-of-apps/pull/27
https://github.com/splunk/ta-automation-k8s-manifests/pull/102
splunk/addonfactory-workflow-addon-release#344

@awownysz-splunk
Copy link

pawel-dabro
pawel-dabro previously approved these changes Dec 12, 2024
Copy link

@pawel-dabro pawel-dabro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, but pls see comment about documenting more precisely which way the upgrades work.

action.yaml Outdated
default: ''
ta-upgrade-version:
required: false
description: 'upgrade version of TA'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we make it clearer that this is the "pre-upgrade" version to run with? Or is it the other way around?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Description adjusted

@awownysz-splunk awownysz-splunk force-pushed the feat/ADDON-73868-add-inputs-for-upgrade-tests branch from 9bc7fd7 to 0ea5138 Compare December 17, 2024 09:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants