feat: upgrade tests #344
Open
feat: upgrade tests #344
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Upgrade tests documentation linked here: https://splunk.atlassian.net/wiki/spaces/PROD/pages/1078712566765/Upgrade+Tests+Automation |
awownysz-splunk
force-pushed
the
feat/ADDON-73868-implement-upgrade-tests
branch
from
355238a to
ea4a921
Compare
Co-authored-by: Adam Wownysz <[email protected]>
awownysz-splunk
force-pushed
the
feat/ADDON-73868-implement-upgrade-tests
branch
from
ea4a921 to
771d953
Compare
|
Additional details about changes in this repo:
|
pawel-dabro
previously approved these changes
Dec 13, 2024
| @@ -675,7 +698,13 @@ jobs: | |||
| name: package-deployment | |||
| path: build/package/deployment** | |||
| if: ${{ !cancelled() }} | |||
|
|
|||
| - name: app-id | |||
There was a problem hiding this comment.
I believe this is not necessary after switching logic of accessing packages from splunkbase to aws s3.
| vendor-version: ${{ matrix.vendor-version.image }} | ||
| sc4s-version: "No" | ||
| k8s-manifests-branch: ${{ needs.setup.outputs.k8s-manifests-branch }} | ||
| app-id: ${{ needs.build.outputs.app-id }} |
There was a problem hiding this comment.
app-id is no longer necessary
awownysz-splunk
force-pushed
the
feat/ADDON-73868-implement-upgrade-tests
branch
from
a4d72db to
44dbcef
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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/wfe-test-runner-action#35