-
Notifications
You must be signed in to change notification settings - Fork 3
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
base: main
Are you sure you want to change the base?
Conversation
Upgrade tests documentation linked here: https://splunk.atlassian.net/wiki/spaces/PROD/pages/1078712566765/Upgrade+Tests+Automation |
There was a problem hiding this 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' |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Description adjusted
b4ae176
to
9bc7fd7
Compare
9bc7fd7
to
0ea5138
Compare
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